Questions about ArchtSoft, answered directly
Straight answers about what ArchtSoft is, how it governs AI coding agents, how it differs from enterprise architecture tools and coding assistants, and what stage the product is actually at.
ArchtSoft is an architecture-driven AI engineering platform built by GRIPACS. ArchtSoft holds one structured, versioned, approved architecture model at the centre of the software engineering lifecycle, and requires AI agents to read from that model before they build anything. The result is that implementation derives from the approved architecture rather than interpreting a document, and every artifact remains traceable back to the requirement that produced it.
ArchtSoft governs AI coding agents by making the approved architecture model a precondition for action. An agent cannot act on an architecture model that has not been reviewed, versioned and locked, and the approved model defines the scope each agent may touch. Every model call routes through a single AI gateway, giving one enforcement and observation point across the platform, and six specialist agents — coding, database, review, test, integration and deployment — carry defined responsibilities instead of one general-purpose agent doing everything.
An AI coding assistant helps a developer write code faster inside the editor. ArchtSoft decides what should be built and whether what was built matches the approved design. The structural difference is the approval gate: a coding assistant will generate whatever is asked of it, whereas ArchtSoft agents cannot act on an unapproved or unversioned architecture model. ArchtSoft is complementary to coding assistants rather than a replacement for them.
Established enterprise architecture tools are systems of record for documenting an architecture and reporting on an application portfolio. ArchtSoft is designed to enforce the architecture rather than document it: the model is versioned and approved, drift between the designed and running system is detected against that version, and AI agents execute tasks derived from the model. ArchtSoft also covers simulation before implementation, which traditional EA tooling does not provide.
Architecture drift is the growing gap between the architecture an organisation approved and the system it is actually running. Drift accumulates whenever a change is implemented without updating the design, and it is usually invisible until remediation becomes expensive. ArchtSoft detects drift by comparing the deployed system against a specific approved version of the architecture model, so the gap is reported against a baseline rather than discovered during a review.
ArchtSim is the ArchtSoft module that simulates architecture behaviour before implementation. ArchtSim evaluates component and service interactions, latency, throughput, capacity and bottlenecks, component and dependency failure scenarios, behaviour under varying workloads, and projected cost across competing architecture options. The purpose of ArchtSim is to surface design weaknesses on the model, while changing the design is still cheap.
ArchtSoft can replace an existing enterprise architecture tool, but that is rarely the starting point. Most teams begin by modelling one bounded domain in ArchtSoft alongside what they already run, review the drift report, and widen the scope once the governed model has earned its place. ArchtSoft's difference from a conventional EA tool is that the model is enforced against implementation rather than maintained as documentation.
ArchtSoft agents write code only within a scope that the approved architecture model defines, and only once that model has been locked. Agents cannot act on an unapproved or unversioned model. Each agent carries a defined role, and the orchestrator owns task assignment, dependencies, retries, validation and approvals.
ArchtSoft's architecture modelling, cost estimation and region design cover AWS, Azure and Google Cloud Platform. The ArchtSoft platform itself targets multi-tenant deployment on AWS, with private deployment options available on the Enterprise tier.
ArchtSoft models the current state of an existing architecture first, then reports the drift between that model and what is actually deployed. For most teams that drift report is the fastest way to judge whether architecture governance is worth adopting, because it is produced from the real estate rather than from a sales demonstration.
ArchtSoft does not currently hold SOC 2 Type II or ISO 27001 certification, and GRIPACS does not offer a HIPAA business associate agreement at this stage. Control mapping against those frameworks is complete and available for review, but a mapping is not an audit. When an auditor is engaged, the firm, the scope and the report date will be published on the ArchtSoft trust centre.
ArchtSoft records decision and generation lineage designed against EU AI Act Article 12, which covers logging and record-keeping, and routes all model calls through a single AI gateway so that lineage is captured at one point rather than reconstructed afterwards. Under the Digital Omnibus agreed in 2026, high-risk obligations for Annex III systems apply from 2 December 2027 and Annex I systems from 2 August 2028.
ArchtSoft is licensed annually and priced on the scope of architecture governed rather than per seat, so no list price is published. Three tiers are available: Team for a single architecture team, Growth for multiple teams sharing one governed model, and Enterprise for organisation-wide governance with assurance and private deployment requirements. Pricing is quoted against a defined scope.
ArchtSoft uses a three-layer tenant isolation model separating data, execution and access. All model calls pass through a single AI gateway that acts as the enforcement and observation point. A STRIDE threat model covers 27 identified threats across 10 platform components, security controls are mapped against NIST 800-53 Rev 5, and an outbox pattern replicates audit records independently of the primary transaction path.
ArchtSoft is in active development and working with early design partners rather than at general availability. GRIPACS states explicitly which capabilities are implemented today and which are on the roadmap, and the ArchtSoft trust centre marks each item accordingly rather than presenting planned work as shipped.
ArchtSoft is built by GRIPACS, a small technically-led company based in Shrirampur, West Bengal, India, founded by Sougata Chakraborty. Enquiries are answered by the people who build the product rather than by a sales development team.
The terms used on this site
Architecture governance has a vocabulary that is used loosely elsewhere. These are the definitions ArchtSoft works to.
Architecture governance
Architecture governance is the practice of ensuring that the system an organisation runs matches the architecture it approved. Governance becomes enforcement rather than paperwork when the approved design is versioned and implementation is derived from it.
Architecture as a control plane
Treating architecture as a control plane means the architecture model actively directs and constrains what gets built, rather than describing it after the fact. The model becomes a runtime input to the engineering process instead of a document.
Architecture drift
Architecture drift is the widening gap between an approved design and a running system. Drift accumulates with every change implemented without updating the model, and is typically discovered only when remediation has become expensive.
Traceability chain
A traceability chain links each deployed artifact back through integration results, test evidence, code, development tasks, architecture components and decisions, to the business requirement that caused it. An unbroken chain turns an audit into a query.
Architecture simulation
Architecture simulation evaluates how a proposed design will behave — latency, throughput, failure modes, scaling and cost — before implementation begins, so that weaknesses surface while the design is still inexpensive to change.
Question not answered here?
Send it over. You will get a reply from someone who builds the product, not from a sales development queue.

