Data residency and sovereignty
Under BYOC the platform, control plane included, runs in your own AWS, Azure, GCP, OCI or data center account. No cost, usage, telemetry or workload data leaves your infrastructure.
Enterprise architecture
N0 · The gate
Can this even run inside our estate?
In a regulated account this question is answered before anyone looks at a dashboard, and it is answered by people who do not attend the demo. Bring Your Own Cloud is how DigiUsher passes it.
Signed off by the security board, enterprise architecture and procurement
The distinction
Software that runs in your account is a supply decision. Software that holds your data is an outsourcing arrangement.
What the gate covers N0.1 N0.2 N0.3 N0.4 N0.5 Why it matters Deal shape
Five checks, each owned by someone outside the buying team.
Security review pass
Keys stay in your own KMS and are never exported, shared or escrowed. Data is immutable in your account and queryable from your SIEM. SOC 2 Type II and GDPR apply to the hosted models.
Security board
Network reality
Connectors are outbound only, with signed payloads and no inbound traffic. Prompts, responses and tool payloads are discarded at ingestion by rule, whatever the connector configuration.
Network and platform engineering
Commercial model at scale
A flat annual subscription by consumption tier, never a percentage of spend. A supplier paid as a share of your bill has no reason to want the bill smaller.
Procurement and finance
Delivery and procurement path
Available through global systems integrators including Infosys, Wipro, Coforge, Persistent Systems and Hitachi Digital, directly, or on AWS and Azure Marketplace against existing commitments.
Procurement and vendor management
This check is binary, and it is usually made before us.
When residency and perimeter rules are live, most cost platforms are ruled out on architecture rather than on features. That distinction lets vendor risk teams treat DigiUsher as software supply rather than an outsourcing arrangement.
The architecture
Three deployment models, one feature set.
The same platform, in the place your regulator and your architecture board can accept.
Your environment
Your cloud account
VPC · cost data · usage logs · billing exports · k8s metrics
DigiUsher
Control plane
Metadata only · dashboards · forecasts · alerts
Under BYOC the whole platform, control plane included, runs inside your perimeter. Individual-level views are RBAC-gated, with an organization-wide aggregate-only mode for works-council and compliance postures. There is an audit record of every connector, credential and visibility change.
Everything your security review will ask for, in one place.
A 15-minute call about your stack, then first insight within 48 hours of onboarding.