Skip to main content
Write with AI. Run locally. Deploy to Xano. This section is the first step. Your coding agent writes the database, the APIs and AI agents in TypeScript with the Xano SDK. Each piece is a def object: a table, an endpoint, an agent, a task. You register def objects on one workspace() in xano/index.ts, and the SDK compiles them into the backend that runs on the Xano Engine on your machine, then on Xano when you ship.
Everything is typed. A renamed column is a compile error in every endpoint that reads it and in the frontend that renders it, so mistakes surface in your editor rather than after a deploy.

Which kind do I use?

Choose by who or what starts the work.

Pages in this section

Your first change

Add a table and an endpoint, deploy to the Xano Engine, and call it.

Data and tables

Columns, foreign keys, indexes, seed rows, queries, addons and table triggers.

APIs, functions and middleware

API groups, endpoints, reusable functions, background runs, auth and middleware.

Tasks and platform events

Scheduled jobs, and triggers for Xano branch changes and new errors.

Realtime

Websocket servers, channels, message handlers and their connection triggers.

AI agents and MCP servers

Agents, tools, MCP servers, knowledge, and what each connection sees.

Custom code

Lambdas, HTTP calls to other services, and microservice containers.

Tests

Unit tests and workflow tests that ship with your code.

Environment variables and secrets

Declare names in code, keep values out of git, rotate safely.

Typed frontend

Call your endpoints with types generated from the backend.

Add-ons

Install auth, vector search, validation and more from the marketplace.

Where to go next

Start with your first change. For every builder, field type and option, see the authoring reference and the object kinds reference.