Skip to main content
Xano gives you a genuinely scalable backend — Postgres, serverless functions, background tasks, realtime, MCP servers, AI agents — without you running a single server. XanoTS is Xano’s officially supported TypeScript SDK, and it gives you that backend as code you own: version it, review it in PRs, diff it, roll it back.

Quickstart

Empty folder to a live full-stack app, in four commands.

The model

Def objects, one workspace, one importable bundle.

​
Why XanoTS

TypeScript is the source of truth

Tables, indexes, endpoints, functions, triggers, tasks, middleware, AI toolsets — all typed TS in your repo. No clicking through a dashboard and hoping prod matches staging.

Deploy is built in

xanots deploy compiles your code, ships it over an authenticated connection, and prints the URL. Backend and static frontend in one command.

Fast, safe iteration

Ephemeral environments are disposable and auto-expiring. Deploys are identity-stable — re-running never duplicates objects, and with a committed xano.lock renames stay renames.

Types flow to your frontend

Import a query() def into your React/Svelte/Angular app and get the path, verb, and a fully-typed payload — with zero codegen.
AI-first by design. A deterministic, fully-typed authoring surface means an agent (or you) emits well-typed TS that always compiles to a valid, importable workspace. It ships with machine-readable grounding an agent reads instead of your source — see Coverage & agent grounding.

​
Start here

The scaffolded project

What xanots init writes — the two frontend presets, theming, and add-ons.

Object kinds

Every authorable primitive, and splitting a workspace across microservices.

Authoring reference

Tables and fields, statements, values, inputs, middleware, request history.

Signing in & deploying

Auth, ephemerals, --static, releasing to production, and xanots preflight.

The typed frontend surface

Path resolution, input and response inference, and what the import costs.

CLI

Every command, shell completion, and what failures look like.

​
Already have a Xano workspace?

xanots init my-app --from workspace pulls your existing backend down as TypeScript — tables, endpoints, functions, triggers, and settings — and writes a report of anything that did not survive the round trip. See Pulling an existing workspace.