Run the tests from the CLI
Tests on queries, functions and middleware, plus standalone workflow tests, run against the Xano Engine or ephemeral you last deployed to, or your real workspace.
Xano for developers: Built to be verified.
Your workflow, intact: CLI, tests, branches, and your agents, with what runs underneath specified in enough detail to check.
The toolchain
A toolchain you'll recognize.
Everything a serious backend expects, on a platform your whole team can see into:
Ephemeral environments
Unlimited sandboxes per workspace, and disposable tenants for parallel work: spin one up per change, run the tests against it, promote it, or throw it away.
Write it in code, read it anywhere
Your TypeScript in the repo is the source. Deploy it, and Canvas View and the Function Stack show what it compiled to, readable by everyone on the team. Already on Xano? init --from workspace pulls your workspace back as TypeScript.
Build the whole backend in TypeScript
With the Xano SDK, tables, APIs, realtime channels, tasks, MCP servers and AI agents are all TypeScript objects in your repo. Run them on the Xano Engine on your machine, then deploy the same code to Xano.
Bring your own runtime
Run any workload as a Docker microservice alongside your governed logic, with business rules and observability wrapped around it.
APIs, documented automatically
Every endpoint ships with autogenerated OpenAPI docs, so what's documented matches what runs.
Version everything
Branching and merging, draft changes with revertible history, and a full change record for every object.
Your editor, your repo
Tables, endpoints, functions, tasks and AI toolsets are typed TypeScript in your repo. Version it, review it in pull requests, diff it, roll it back. Prod matches staging because they are the same commit.
Start to shipped
From your IDE, start to shipped.
Your agent, grounded in the Xano SDK’s typed API, from pull to promote.
- Claude Code
- Cursor
- VS Code
- ChatGPT
- Copilot
- Codex
-
$ npx @xano/sdk agent-skill install# the xano-backend skill, in each coding agent on this machine -
$ npx @xano/sdk init my-app --from workspace# your backend, on disk, as TypeScript -
> "Add a signup endpoint that emails a welcome message"# the agent writes it -
$ npx xanosdk deploy --ephemeral --test# deploy to a disposable ephemeral and run the tests -
$ npx xanosdk release create v1# the stored record that this code came up and answered -
$ npx xanosdk promote v1# land the release on your workspace
Signals on the line
See where it broke. Ship only what you approved.
Debug
When something breaks, you see where. Immediately.
Stack traces that point to the failing stack, not a log dump. Step-through of functions with production data. Request history across every endpoint. An audit trail for every change, human or agent.
Release
Nothing ships that you didn't approve.
The release flow is the same everywhere: sandbox → immutable artifact → review → promote. The exact artifact your team inspected is what runs in production. Tenants give each client, region, or cohort its own database, URL, and lifecycle.
CI/CD and tenants Where it runs
Your cloud or ours. Any region. In a click.
Deploy
Standard substrate, no surprises.
Regional deployment in a click, across cloud hosts and hosting configurations. The common enterprise journey: start in your cloud, and hand over operations when we've earned it.
Xano runs on technology your platform team already operates:
- Kubernetes
- Postgres
- Redis
Managed
Xano operates it end to end.
Bring your own cloud
Deploys into your AWS, Azure, or GCP: your jurisdiction, your keys.
Self-hosted
Including on-prem, for the environments that require it.
Further down the line
The same principle, all the way down.
- 01 · Operate
Understanding doesn't stop at your application.
Autopilot brings the same principle (see it, trust it, prove it) to the infrastructure your software runs on: continuous right-sizing of every pod, node, and autoscaler, applied in place.
See Autopilot - 02 · Secure
Security, built into the platform.
Stateless handling of personally identifiable information. Workload isolation. A request-history off-switch. No training on customer data.
Security & compliance
Questions
Xano for developers
How do developers build a backend with Xano?
Build your backend in TypeScript with AI. Your coding agent (Claude Code, Codex or Cursor) writes it with the Xano SDK, you run it on the Xano Engine on your machine, then deploy it to Xano. Tables, APIs, tasks, MCP servers and AI agents are all TypeScript objects in your repo.
Can I run Xano tests from the CLI?
Yes. npx xanosdk test run-all runs tests on queries, functions and middleware, plus standalone workflow tests, against the Xano Engine, the ephemeral you last deployed to, or your real workspace. npx xanosdk deploy --ephemeral --test deploys to a disposable ephemeral and runs the tests there.
Does Xano work with Git and pull requests?
Yes. Tables, endpoints, functions, tasks and AI toolsets are typed TypeScript in your repo, so you version, review, diff and roll them back with the Git workflow you already use. Prod matches staging because they are the same commit, and every object keeps a full change record.
Can I move an existing Xano workspace into code?
Yes. npx @xano/sdk init my-app --from workspace pulls your workspace back as TypeScript, so your backend is on disk where your coding agent can work on it. After you deploy, Canvas View and the Function Stack show what the code compiled to, readable by everyone on the team.
Where does Xano run?
Wherever you need it: managed by Xano end to end, deployed into your own AWS, Azure or GCP (your jurisdiction, your keys), or self-hosted, including on-prem. Underneath is a standard substrate your platform team already operates: Kubernetes, Postgres and Redis, with regional deployment across cloud hosts.