Why build all of this.
ATS Technologies has run other people's mail servers, phone systems and networks for a long time. IronMesh started because the answer to "can we keep this in the building" kept being no.
Every year more of what a business depends on moved into a subscription that could be repriced, changed or withdrawn, on infrastructure its owner could not see. For most companies that trade is fine. For some — a firm with regulatory obligations, a client on a bad line, an operation that cannot stop when a distant service has an outage — it is not.
There was no complete alternative to point those customers at. There were parts: a mail server here, a file sync tool there, each with its own login and none of them aware of the others. So we built the set, and made them share one identity, one permission model and one control panel.
It has to run in both places
Every product installs on a server in your building and on our infrastructure, from the same build. Nothing is withheld from the on-premises version to make the hosted one more attractive. That constraint has cost us features; it is also the entire point.
No copyleft in the stack
Software licensed under the AGPL or GPL cannot be shipped inside a product a customer installs and owns without conditions most businesses will not accept. So every component was chosen — and in several cases written from scratch — to avoid it. IronIngot exists largely because the document editor we were paying for charged per user.
Built by the people who support it
Every product is built by the same team to work on its own and alongside the rest. When something needs attention, you are talking to the people who wrote it.
Run it on your own servers, wherever they are, or on ours, which are operated by the same people who answer the phone. IronForge — the hosting arm — carries the rest of the suite, which means we find out about a problem the same way you would, at the same time.