Product catalog
Choose what your business runs on, what your engineers build with, or an outcome we operate for you. Every page states the price, hosting, licence, and ownership model.
For the person who signs the invoice
The software your company operates on — industry platforms, support, hiring, contracts, consent. Each one replaces a SaaS invoice you resent, and you own it outright.
4 products
For the team that ships the code
The infrastructure under your own software — model routing, retrieval, identity, search, observability, testing. Self-hosted, unmetered, and yours.
4 products
For outcomes that need a team
Productised services with a defined outcome: build the software, run the quality function, or establish a customer-owned capability.
3 services
Not for sale — what sprints are built from
3 components
These are the building blocks behind our fixed-price sprints. We use them in delivery, but do not sell or support them as standalone products. When one is ready for that promise, it appears above with clear terms.
Need something that isn't on this page? Scope a custom sprint — you'll see the price band immediately, and a fixed price lands within one business day.
Compliance & data boundaries
Owned software, hosted products, open source, and human-delivered services do not share one data boundary. Each offer states where it runs, who operates it, what the customer controls, and which terms must be set in scope.
Owned
Customer-hosted software
Choose the cloud account, region, database, keys, and access model during implementation. The deployment record — not a generic trust-page sentence — establishes residency.
Managed
Verity & Clearpath
These are hosted products. Their plans state what is metered and whether self-hosting is available; processing, retention, and residency terms are agreed for production use.
Services
Sprint & QAShift
Repository access, production access, data handling, retention, and revocation are defined in the engagement scope and limited to what delivery requires.
GCC
Partner-led workstreams
ResoluteX coordinates the programme. Employment, legal, payroll, tax, accounting, insurance, and other regulated specialists remain named and accountable for their work.
AI products disclose the gateway, provider keys, hosting path, and any model-provider processing before production use. A customer-hosted Vyom deployment is different from a managed AI feature, and the site no longer describes them as if they were the same.
For customer-hosted software, residency follows the region you deploy. For managed products and services, it follows the contracted hosting and processing terms. The product page tells you which conversation you are in.
Where audit trails, consent records, access logs, or evidence exports are part of the product or scope, their location, retention, and export path are documented and testable.
Products can integrate with Vyom when customer-controlled routing is required. AI Architect and the current Relay reference widget use OpenRouter directly today; we will not label them as Vyom deployments until that integration exists.
Running the consent and cookie side of this yourself? That's Custodian — the banner on this page, which you can also own. Full detail in the privacy policy.