By David,
Vendor trust is a fine thing, and the security industry runs on carefully constructed versions of it: SOC 2 reports, DPAs, pen-test summaries, region commitments. But every one of those artifacts exists to answer the same underlying question - what is the vendor doing with our data in their environment? - and there's a category of buyer for whom the best possible answer is: there is no vendor environment.
That's the claim behind "customer-owned infrastructure," and because the phrase gets marketed loosely, this article pins down what it means concretely for Atlas Ink, what it doesn't mean, and where it actually changes outcomes.
What you own, specifically
Deploy Atlas Ink and the platform lands inside your own Azure subscription:
- The compute is yours. The service runs on an App Service in your subscription, subject to your network rules, your conditional access, your resource locks.
- The database is yours. Templates, scoped assignments, revision history, rollout status - all of it in a per-tenant PostgreSQL database you own. There is no multi-tenant vendor database with your rows in it.
- The keys are yours. Encryption keys live in your Azure Key Vault, under your access policies and your rotation schedule.
- The boundary is yours. The whole deployment sits inside the security perimeter your organization already governs - the same policies, the same logging, the same SIEM.
What crosses that boundary in normal operation is exactly one thing: an aggregate count of distinct active users per month, reported to Atlas so it can bill $1 per active user, always. Not mail - no message ever routes through Atlas. Not directory data - Entra ID is read in place, read-only. One number.
What customer-owned is not
Three adjacent concepts get sold under similar language, and the differences are load-bearing:
It's not single-tenant hosting. "You get your own instance" usually means a dedicated slice of the vendor's cloud - separated from other customers, but still the vendor's subscription, the vendor's operators, the vendor's keys. Isolation improved; ownership didn't.
It's not region selection. "Choose your Azure region" answers the jurisdiction question - EU data stays in the EU - but the processing is still the vendor's. If your requirement is "within our tenant" rather than "within our borders," region choice is an approximation. The Crossware comparison works through exactly this distinction, because it's the sharpest version of it in the signature market.
It's not self-hosted DIY. Owning the infrastructure doesn't mean operating the software alone. Atlas Ink is deployed and updated as a product; what you take on is standard Azure resource hygiene you already do at scale, not a bespoke server to patch. (The self-hosted vs SaaS breakdown maps this middle ground properly.)
Where ownership changes outcomes
The risk profile. A vendor-hosted signature platform is one breach away from exposing many customers' directory data at once - that's what multi-tenant means. When the platform runs in your subscription, there is no shared service holding your data to breach. Your exposure rides on your own tenant's security posture, which is where you're already investing.
The audit story. "Where is signature data stored, who accessed it, and how is it encrypted?" becomes a set of Azure Portal screenshots instead of a vendor questionnaire round-trip. The platform's audit logs are your logs, in your Log Analytics, on your retention schedule. For regulated industries - government, healthcare, finance - that difference is often the difference between a finding and a footnote.
The exit options. Leave a SaaS and your offboarding is a deletion request plus trust. Decommission an in-subscription deployment and you delete the resource group. The data was never anywhere else; there's nothing to chase.
The dependency math. Your signatures don't depend on a vendor's uptime, because provisioning runs from your infrastructure - and even if the push service were down, signatures already written into mailboxes just keep working. There's no stamping service in the delivery path to fail.
What running it looks like
Ownership is simple to run. You pay Azure directly for the (small) infrastructure the deployment consumes, alongside the per-user software meter, at cost and on your own invoice. Your team applies the same tagging, monitoring, and access review you already use for any subscription resource. And because nothing sits in your mail path, there's no stamping service to review, monitor, or fail.
The one-sentence test
Ask any signature vendor: "If we deleted your company tomorrow, where would our data be?" For a hosted platform, the honest answer is "in our environment, pending offboarding." For Atlas Ink, the answer is: exactly where it always was - in your subscription, under your keys, behind your boundary.
That's what customer-owned means when it's structural. The data-residency walkthrough traces the flows in detail, and the Atlas Ink page shows the deployment end to end.