Skip to content

Software we stand behind.

Assessment, advertising, voice and intelligence. Software we operate and license, with the controls our Enterprise clients require. Available through self-serve, enterprise and managed arrangements.

Sculptural optical glass and polished titanium in white light.

Why a services firm ships products.

The suite carries the same operational commitments as an Enterprise engagement: tenant isolation, audit trails, regional hosting and exportable data. Licensing follows the deployment, from self-serve access to enterprise agreements and managed operation.

Every Enterprise mandate leaves behind a system. Most of them are the client's and stay the client's. A few solve a problem so general — an examination that has to be defensible, an advertisement that has to exist by Friday, a phone line that has to answer in three languages, a board that has to know what changed — that building them once, for one client, would be the wrong decision. Those become products.

The products are held to the standard of the practices that built them. The same people who design data residency for a private bank design it for the suite; the same evaluation discipline that gates a client's model gates the models inside the products. A product that would embarrass the firm in an Enterprise procurement does not ship.

It also keeps the firm honest in the other direction. Operating software for many customers, month after month, teaches lessons about reliability, support and cost that a project team never learns. Those lessons go back into every Enterprise engagement.

The suite.

Four products, two of them live today on their own domains, two licensed to enterprise clients as the productised form of an Enterprise practice. Each has its own page: what it is, what it does, the controls it ships with, how it integrates and how it is licensed.

How the products are licensed.

Three ways to hold a product, chosen per product and per client. The tier decides who operates it and where it runs; the software is the same.

Self-serve
Sign up, pay by subscription, operate it yourself. Available where a product is designed for it, with the standard controls, standard regions and the published terms.
Enterprise licence
A negotiated agreement: single sign-on, your identity provider, a chosen hosting region or your own data plane, a signed data-processing agreement, named support and a service-level schedule. Procurement's questions are answered in the agreement, not in a help page.
Managed by Altuon
The product operated for you as part of an Enterprise engagement — configured, integrated, monitored and improved by the practice that built it, under the engagement's governance.

The controls every product ships with.

The same controls the Enterprise practices are asked for, built into the suite rather than promised for a later release.

Tenant isolation
Each customer's data is separated at the storage and access layers; no query can cross a tenant boundary, and isolation is part of the release test suite.
Audit trail
Who did what, when, to which record — retained, exportable and readable by your own auditors.
Regional hosting
A hosting region chosen per enterprise agreement — Switzerland, the European Union or the United States — or deployment into your own data plane where the product supports it.
Identity and access
Single sign-on with your identity provider, role-based access, least privilege by default, and administrator actions logged.
Exportable data
Everything you put in and everything the product produces can be exported in open formats. Leaving is a documented procedure, not a negotiation.
Model governance
Where a product uses language or vision models, the model version, its evaluation results and its data-handling terms are documented, and your data is not used to train models for other customers.

How the products fit what you already run.

Each product exposes its data and its actions through documented interfaces — single sign-on for people, application interfaces and webhooks for systems, exports for everything else — and each is built to sit beside your existing systems of record rather than replace them. Identity comes from your provider, not from a separate set of passwords; events leave the product the moment they happen, so your own systems are never waiting on a nightly file. Where an Enterprise engagement is in place, the practice integrates the product into your landscape as part of the mandate, under the engagement's governance and its data-plane decision.

See the products, or ask for the enterprise terms.

The live products open on their own domains. For an enterprise licence, a hosting region or a data-processing agreement, request a proposal and the product team will answer.