Snapshot 95040

Document
Security page
URL
https://www.xano.com/security/
Fetched
HTTP status
200
Content type
text/html; charset=utf-8
Fetch mode
static
Size
143045 bytes
SHA-256 (raw)
2e889c6c376ddf6467b14e128ef164959baf016ead604b4cf9aa313dcb45c6ed
SHA-256 (normalized text)
b3fc1e95f6c714fae65fae58411c4049b803bc29f2696d08b758985bf3d4f96e

Normalized text

Scripts and page chrome removed; this is what change detection compares.

Security your IT team can verify, not just read about.
Certifications are the starting point, not the story. Everything beyond them is inspectable: every endpoint, every change, every approval, and who or what made it, visible to the team that answers for it.
Start building, free Talk to sales
How AI code governance works
Certifications
ISO 9001 · SOC 2 Type 2 · SOC 3, independently audited.
SOC 2 TYPE II
SOC 3
ISO 27001
ISO 27701
ISO 9001
HDS
DPF
GDPR
HIPAA
CCPA
FERPA
PIPEDA
LGPD
HIPAA-compliant apps Security guide Trust center
Frequently asked questions
Because they can see it, control it, and prove it, without taking our word for any of it. The next three answers break that down.
Every endpoint, every change, and who or what made it. The workspace is the live system, not documentation that drifts: the business logic, the APIs it touches, and the full change history are readable by the engineer who inherits it and the risk team that answers for it. When an agent makes a change, it’s attributable, timestamped, and reviewable the same way a person’s is.
The harness. Your team sets the rules once and every build inherits them: which auth patterns and identity stack apply, who can access what (RBAC, enterprise SSO), where data lives (region and residency), which code dependencies are allowed, and which review gates a change must clear before it ships. Nothing reaches production except the immutable release your team inspected and promoted; policy is enforced during the build, not reported after the fact.
Audit logs, full request history, version history, and rolling backups: the record of what ran, when, and on whose approval, alongside the certifications listed above. PII handling is stateless, request history has an off-switch, and we don’t train on customer data.
Yes. Everything you build in Xano is exportable. Your data lives in a standard Postgres database and exports directly; at volume, we help you move it. Your logic, schema, and tests are readable and translatable to the language of your choice, with AI assistance and a human in the loop.
Yes. A BAA is part of the Enhanced security add-on (HIPAA + BAA and more). HIPAA is a paid add-on on the Pro plan and included on Custom plans; see pricing. For how Xano’s infrastructure, isolation model, and security features support HIPAA-aligned workflows, read the guide to building HIPAA-compliant apps.
AI builds software.
Xano makes it trustworthy.
Start building, free Talk to sales