Enterprise
Enterprise is one agreement between your organisation and us, covering everybody in it. No new tier, no upgrade, nothing your people have to learn — the same platform they are using today, with everything that matters to the company written down and signed.
Starting from CHF 9,500 a year. Priced for the organisation, not per person — the rate is agreed rather than read off a list, and what moves it is size and how much of the platform you turn on.
You do not need a requirements document — a list of questions is enough.
Your CRM is good at being a CRM. Finance, the ticket queue, the design tools — each chosen by people who knew what they needed, each better than anything trying to do all of them. None of them knows about the others.
AI arrived the same way, one team at a time, each purchase reasonable. But software does not answer for itself. Who set the limit for the whole company? Who decided what the finance team’s assistant may reach? Who signed for the data? Nobody has agreed to. That is what Enterprise is.
Question 01
Who set the limit for the whole company?
Name
Question 02
Who decided what finance’s assistant may reach?
Name
Question 03
Who signed for the data?
Name
Three questions a company is expected to answer. Today none of them has a name against it.
It starts making sense where somebody other than the user has to answer for the tool — a governance threshold, not a headcount.
Somewhere real
TVB Mayrhofen — an Austrian tourism board — runs its own knowledge through the Smart Company OS in daily guest-services work. Not an organisation of a thousand people, and we will not pretend otherwise. It answers a different question: whether this runs somewhere real.
Other organisations have run proof-of-concepts on it, and we run Aitronos on it ourselves — our own documents, our own questions, every working day.
Spending limits organisation-wide and per key. Quotas per person, so one team’s experiment cannot eat the budget. Usage broken down per person, per department and per model — so the report answers who, not only how much.
Seven roles out of the box, Owner down to Guest, and three presets — collaborative, balanced, controlled. Departments in a tree matching your own, managers scoped to their branch. Guest is a hard boundary: five capabilities, every organisation-wide sharing path closed.
EU and Swiss residency as a contract term, not a setting somebody ticked. Where that is not enough, models, knowledge and automation can run on infrastructure you control — the furthest being the Aitronos Box: the whole platform on a machine in your building, specified for what you run. Arranged, not selected from a menu.
Named contacts, not a queue. A coverage window, response times by severity, an uptime target we commit to, and an allowance of our people’s time for implementation and training. Each is set in the agreement, which is why no figure is printed here.
Not development to order. What an organisation on this agreement asks for goes to the people who set the roadmap, and weighs more there than any single user’s request.
A data processing agreement, and the compliance commitments your legal and security teams require. A usage and volume agreement, so the metered half of the bill is bounded in advance. One invoice, not a card per department.
More than a thousand systems already connect, and a knowledge source can be almost anything you already store. If the one your work actually runs on is not among them, we build the connector for it — any system, at no cost, for as long as the agreement runs. It is the one thing on this page we do build to order, and it never becomes a line on the invoice.
You are going to forward this to a reviewer. Most of what comes back is already answered here.
Certification held?
ISO/IEC 27001:2022 — IC-IS-2606004
Audit trail?
Tamper-evident, exportable
Deletion and export?
GDPR Art. 17 / Art. 20
Tenant separation?
Every organisation isolated
Our own retention policy?
Yours to set
The signed certificate is one press away — the PDF exactly as InterCert issued it. The policy library, the sub-processor list and the data processing agreement can be requested from the Trust Center at trust.aitronos.com. Send your reviewer straight there; you need not be in the room.
Not a demo. A conversation with the people who would run your deployment: what you already have and what would connect first. You leave with the certificate and the data processing agreement whether or not it goes further.
You do not need a requirements document — a list of questions is enough.
