Priced on the scope you govern, not per seat
Licensing depends on how much of the estate the model covers, which modules you run, and your deployment and assurance requirements. We quote against a scope rather than publishing a number that would be wrong for most teams.
Team
A single architecture team proving the model
- Core architecture modelling and versioning
- ArchtSpec and ArchtGen
- Up to 5 seats
- Community support
Growth
Multiple teams sharing one governed model
- Everything in Team
- ArchtData, ArchtCloud, ArchtInfra and ArchtSim
- Approval workflows and drift detection
- SSO and role-based access
- Priority support
Enterprise
Organisation-wide governance with assurance requirements
- Everything in Growth
- ArchtSec, ArchtCompliance and full agent orchestration
- Private deployment options and tenant isolation
- Compliance evidence, lineage recording and audit export
- Named technical contact and onboarding support
All tiers include the core architecture model, versioning and traceability. Deployment region, data residency and private deployment are configured per agreement.
What is included where
| Capability | Team | Growth | Enterprise |
|---|---|---|---|
| Architecture modelling and versioning | |||
| Requirements traceability (ArchtSpec) | |||
| Solution architecture generation (ArchtGen) | |||
| Data, cloud and infrastructure modelling | — | ||
| Architecture simulation (ArchtSim) | — | ||
| Approval workflows and drift detection | — | ||
| SSO and role-based access control | — | ||
| Security architecture (ArchtSec) | — | — | |
| Compliance mapping and scorecards | — | — | |
| Full agent orchestration (ArchtDev) | — | — | |
| Private deployment and tenant isolation | — | — | |
| Audit export and lineage recording | — | — |
Why there is no list price on this page
ArchtSoft is licensed annually and priced on the scope of architecture you govern, not on the number of people who log in. A published per-seat figure would be wrong for almost every organisation that asks, because two companies with the same headcount can have estates that differ by an order of magnitude.
Four things determine a quote. How much of the estate the governed model covers, usually counted in bounded domains rather than applications. Which modules you run, since security, compliance and full agent orchestration sit in the Enterprise tier. Where the platform is deployed, including data residency and whether you need private deployment with tenant isolation. And what assurance you require, which covers audit export, lineage retention and the depth of the security review your procurement process runs.
Every tier includes the core architecture model, versioning and the requirement-to-artifact traceability chain, because governance that applies to only part of the lifecycle is not governance. Licences run annually. There is no usage-metered billing on model calls, so a quote does not move because your teams used the platform more than expected in a given month.
To get a number, tell us which domains you want governed and what your assurance requirements are. A scoping conversation takes about 45 minutes and produces a written quote rather than a brochure.
What your buying process will ask for
We would rather hand these over at the start than discover them in week six of a review.
- Security architecture documentation and threat model summary
- Control mapping against NIST 800-53, GDPR, SOC 2 and ISO 27001
- Data processing agreement and sub-processor list
- Deployment, residency and tenant isolation options
- Support terms, response targets and escalation path
- Current certification status, stated plainly
Get a quote against your actual scope
Tell us which domains you want governed and what your assurance requirements are. We will come back with a scope and a number rather than a brochure.