.png)
AIMS360 is cloud only apparel ERP hosted on Microsoft Azure. There is no on premise version and no servers for you to own. Redundancy spans availability zones, paired regions and replicated data, and upgrades are in the subscription.
AIMS360 is cloud software running on Microsoft Azure. There is no on premise version, no server for you to buy, house, patch or replace, and no upgrade project that takes your team offline for a weekend. Redundancy, backup and upgrades are part of the platform rather than a line item you fund.
AIMS360 is cloud software. There is no on premise version and no option to install it on a server in your own building. The platform runs on Microsoft Azure, which means the hardware, the redundancy, the patching and the physical security are Microsoft's responsibility rather than yours. You do not buy servers, you do not size them for peak season, you do not replace them in year five, and you do not staff someone to keep them running.
That distinction matters more in apparel than in most industries, because the load is seasonal. An on premise system has to be sized for market week and the pre season order surge, then sits underused the rest of the year. You pay for the peak twelve months a year. Cloud infrastructure absorbs the peak without you provisioning for it.
| What you would own on premise | What happens on AIMS360 |
|---|---|
| Buying and sizing servers | No servers to buy. Capacity is Microsoft Azure infrastructure |
| A server room, power and cooling | Azure data centers, with their own power, cooling and networking |
| Operating system and database patching | Handled as part of the platform, at night, off hours |
| A second site for disaster recovery | Replication to a geographically separate region, included for every customer |
| Hardware refresh every few years | Nothing to refresh. There is no hardware on your side |
| Version upgrade projects | Upgrades are covered by the subscription rather than quoted as projects |
| Someone on staff to keep it up | Nobody on your team owns infrastructure |
AIMS360 is redundant at several levels, and every customer gets all of them. Azure regions are built from availability zones: physically separate data centers, each with its own power, cooling and networking, so one going down does not take the rest with it. Microsoft also pairs regions, so a regional event has somewhere to fail over to. On top of that, your data is held in multiple copies at the primary data center and replicated to a second data center in a geographically separate region. If an entire region went down, your data still exists and your system can be brought up elsewhere.
Physically separate data centers inside a region, each with independent power, cooling and networking. A failure in one does not cascade to the others.
Microsoft pairs Azure regions, so a regional event has a defined place to fail over to rather than an improvised one.
Multiple copies at the primary data center, replicated to a second data center in a geographically separate region.
Continuous backup with restore to any minute in the last 35 days, covered in detail on the data backup page.
None of that is a premium tier and none of it is quoted separately. It applies to every AIMS360 customer, because it is how the platform is built rather than something bolted on for the accounts that ask.
The AIMS360 operating figure has been 99.99%. There is a signed service level agreement attached to the master agreement that commits AIMS360 to commercially reasonable efforts at 100% availability and defines service credits if availability falls below 99% in a billing month. Maintenance does not count against uptime, because it runs at night, off hours.
Two things are worth being precise about here. First, 99.99% is what has happened, not a marketing target: the contractual commitment and the operating record are different numbers and both are stated. Second, the reason maintenance is excluded is that it does not interrupt a working day, which is the only definition of uptime that matters to a shipping department.
Cloud hosted does not automatically mean browser based, and it is worth separating the two rather than letting the word cloud do work it has not earned.
The full AIMS360 ERP runs in Azure and you reach it from wherever you are, an office, a home desk, a showroom during market, a warehouse. Nothing is installed on a server you own and nothing is tied to one building.
Runway is the browser based, mobile friendly platform. It runs from anywhere and on handheld scanners, which is what covers warehouse and scanner work without a workstation.
Being straight about it: the full ERP is a desktop application today, not a web app. That is the part people assume cloud already solves and it is only partly true right now.
Runway gets new features every month. The expectation is that most people will do almost all of their day to day work in the browser within about a year, with the complete version roughly two years out.
The practical version: your infrastructure problem is already solved, your browser access is partly solved and improving on a monthly cadence. If browser access for a specific workflow is what decides this for you, ask where that workflow sits on the roadmap rather than taking a general answer.
The AIMS360 subscription covers technical support, maintenance, training, backup and recovery, upgrades and change management. On premise systems normally quote version upgrades as projects, which is why so many brands run software several versions behind: the upgrade has a price tag and it keeps losing to something else. On a cloud platform there is no version to be behind.
Bug fixes are covered too. For emergency items a fix typically reaches your tenant in about three hours, which is only possible because there is one codebase and one place to deploy it rather than an installation per customer.
It is also worth knowing who builds it. AIMS360 writes the platform, the integrations and the implementation in house. There is no third party to escalate to and wait on, which is the other half of why fixes move quickly.
What sits outside the subscription: IT work, research, data manipulation and consulting are billed separately, and custom programming runs through a statement of work you approve first. Hosting cost movements do reach renewal pricing, since AIMS360 pays Microsoft Azure for the infrastructure, and historic increases have run between three and five percent.
| The assumption | What is the case |
|---|---|
| There is an on premise version if we want one | There is not. AIMS360 is cloud only, hosted on Microsoft Azure |
| Cloud means our data sits in one data center | Multiple copies at the primary data center, replicated to a second in a geographically separate region |
| Disaster recovery is an upgrade | Every customer gets the replicated arrangement at no additional charge |
| We will need an IT person to run it | There is no infrastructure on your side to run. Patching, capacity and hardware are all platform side |
| Upgrades will be quoted as projects | Upgrades, maintenance, support, training and change management are covered by the subscription |
| Cloud means everything runs in a browser | Runway is browser based and mobile friendly. The core ERP is still a desktop application, with the web version expanding monthly |
| Seasonal peaks mean buying capacity for the worst week | Capacity is Azure infrastructure. You do not size for market week and pay for it all year |
AIMS360 is cloud software. There is no on premise version of AIMS360 and no option to install it on a server in your own building. The platform runs on Microsoft Azure, so the hardware, capacity, patching and physical security sit with the platform rather than with your team. You do not buy servers, size them for peak season, replace them in year five, or staff someone to keep them running.
No. AIMS360 is delivered only as a cloud platform on Microsoft Azure. There is no self hosted, private server or locally installed deployment option. If a self hosted deployment is a hard requirement for your business, AIMS360 will not meet it, and that is worth establishing early rather than late.
On Microsoft Azure. Azure regions are built from availability zones, which are physically separate data centers each with their own power, cooling and networking, so a failure in one does not take down the others. Microsoft also pairs regions, so a regional event has a defined failover destination.
Several layers, and every customer gets all of them. Availability zones give physical separation inside a region. Paired Azure regions give a failover destination if a whole region has an event. Your data is held in multiple copies at the primary data center and replicated to a second data center in a geographically separate region, so if an entire region went down your data still exists and the system can be brought up elsewhere. On top of that, continuous point in time backup allows restore to any minute in the last 35 days. None of it is a premium tier.
The actual operating figure has been 99.99%. A signed service level agreement is attached to the master agreement, committing AIMS360 to commercially reasonable efforts at 100% availability and defining service credits if availability falls below 99% in a billing month. Scheduled maintenance runs at night, off hours, and does not count against uptime.
Partly today, and more each month. Runway is the browser based and mobile friendly platform, and it runs from anywhere including on handheld scanners, which covers warehouse and scanner work. The core ERP is still a desktop application today rather than a web app. Runway gains features monthly, with the expectation that most people can do almost all day to day work in the browser within about a year and the complete version roughly two years out. If browser access for one particular workflow is what decides your evaluation, ask specifically where that workflow sits on the roadmap.
No. There is no infrastructure on your side. No servers to buy or size, no server room, no power and cooling, no operating system or database patching, no second site for disaster recovery, and no hardware refresh cycle. For a mid sized consumer brand that is usually the difference between having an IT function and not needing one.
Included. The subscription covers technical support, maintenance, training, backup and recovery, upgrades and change management, so there is no version upgrade project to fund and no way to end up several versions behind. Bug fixes are covered as well, and for emergency items a fix typically reaches your tenant in about three hours. IT work, research, data manipulation and consulting are billed separately, and custom programming runs through a statement of work you approve first.
AIMS360 writes the platform, the integrations and the implementation in house. One vendor is accountable and there is one support queue, with no third party to escalate to and wait on. That is a large part of why emergency fixes move in hours rather than release cycles.
No. Your data is yours and you can export it whenever you want. The open API at api.aims360.com pulls anything out of the system and Live Excel feeds reporting directly into your own files. One practical caution: after termination AIMS360 may erase customer data, so run your final exports before you leave rather than after.
Last reviewed 16 August 2026 by the AIMS360 team.
Reviewed against the AIMS360 hosting, uptime and disaster recovery positions as stated to prospective customers, and against Microsoft's published Azure availability zone and paired region architecture.
If your evaluation has a hosting, redundancy or browser access requirement attached to it, put it in front of us directly and we will tell you where AIMS360 stands on it today rather than where it is heading.
