Developer platform

Build faster with a backend runtime that understands your app.

Generate APIs, data models, permissions, workers, webhooks, storage, and integrations from clean project blueprints — then connect your frontend with SDKs, REST APIs, and AI-assisted workflows.

zsh — shipping-platform
$ zyrostack init shipping-platform
$ zyrostack add auth users roles storage workers webhooks
$ zyrostack generate
✓ 8 entities · 32 routes · 5 workers · 14 policies
$ zyrostack run all
➜ runtime live on :8080
Generated from your blueprint
Database schemaREST APISDK typesPermission rulesWorker jobsWebhook handlersAdmin console
The developer workflow

From idea to backend in one workflow.

Blueprint Generate Run Runtime Connect Frontend Monitor
01
Create a project
Start with the CLI, dashboard, or AI Builder.
02
Define your blueprint
Describe entities, fields, permissions, workflows, modules, and integrations.
03
Generate capabilities
APIs, database tables, workers, events, SDK types, and admin screens.
04
Connect your frontend
Use the TypeScript SDK, REST API, webhooks, or generated OpenAPI specs.
05
Deploy and operate
Run locally, deploy all-in-one, or move to isolated infrastructure later.
Blueprint-first development

Blueprints are the source of truth.

Instead of manually creating routes, tables, policies, jobs, and integration glue, you define the structure once and let ZyroStack generate the working backend layer.

shiptornado.blueprint.yaml
project: shiptornado
modules:
- auth
- organizations
- storage
- webhooks
- workers
- audit_logs
entities:
shipment:
fields:
carrier: enum[ups, fedex, dhl, purolator]
status: enum[draft, purchased, in_transit, delivered]
tracking_number: string?
label_url: file?
user_id: user_ref
permissions:
user:
read: user_id == current_user.id
create: true
admin:
all: true
Generated result
POST /api/shipments
GET /api/shipments/:id
PATCH /api/shipments/:id
shipment.label_created
shipment_status worker
shipment permissions
TypeScript SDK types
One runtime, many modes

Run ZyroStack the way your project needs.

zyrostack
web
worker
scheduler
webhook
all-in-one
run web Serves generated APIs, auth flows, project endpoints, and application traffic.
run worker Processes background jobs, queues, async workflows, email, media tasks, and integration syncs.
run scheduler Runs timed workflows, recurring jobs, billing checks, digest emails, and cleanup jobs.
run webhook Receives and processes external provider events from Stripe, Shopify, eBay, carriers, GitHub, and more.
run all Runs everything together for local development, early-stage projects, and simple deployments.
APIs without repetitive API work

Generate consistent APIs from your data model.

Define an entity and ZyroStack generates secure CRUD routes, validation, permission checks, audit logs, OpenAPI definitions, and SDK types automatically.

Entitylisting
GET /api/listings
POST /api/listings
GET /api/listings/:id
PATCH /api/listings/:id
DELETE /api/listings/:id
Every generated route includes:
Auth required
Permission checked
Rate limited
Audit logged
Typed response
SDKs and API access

Connect from any frontend or service.

const zyro = new ZyroStack({
  project: "assignmentproperty",
  apiKey: process.env.ZYROSTACK_API_KEY
});

const listings = await zyro.entity("listing").findMany({
  where: { status: "active" }
});

await zyro.entity("inquiry").create({
  listing_id: "lst_123",
  name: "Zubair",
  email: "[email protected]",
  message: "I am interested in this assignment."
});
Permissions developers can understand

Permissions live beside your backend model.

Explicit, readable, and tied to generated APIs. Every request is checked before data is returned or modified.

permissions.yaml
permissions:
public:
read: status == active
owner:
update: created_by == current_user.id
admin:
all: true
GET/api/listings
Public can read only active listings.
PATCH/api/listings/:id
Owner can update only their own listings.
DELETE/api/listings/:id
Admin only.
Events, workers, and webhooks

Build workflows without wiring everything by hand.

A generated API can emit an event, a worker can process it, and a webhook can notify another system — all declared in your blueprint.

shipment.created
create_label worker
shipment.label_created
send receipt email
emit customer webhook
workflows.yaml
workflows:
- on: payment.succeeded
actions:
- subscription.activate
- email.send_receipt
- audit.write
- webhook.emit
Integrations for real businesses

Connect the tools your apps depend on.

Each integration: connect · configure · use in workflow · monitor events.

Stripe
SendGrid
Twilio
Cloudflare R2
Shopify
eBay
UPS
FedEx
DHL
Google Maps
OpenAI
Anthropic
GitHub
Slack
Discord
Local development to production

Start all-in-one. Scale when needed.

Local
All-in-one
zyrostack run all
Early production
web + worker
one server
Growing project
Separate processes
web · worker split
Scale
Isolated runtime
dedicated db + workers
Built for AI-assisted development

Let AI propose changes. Keep control before deploy.

AI agents can safely propose entities, workflows, permissions, modules, and integrations. Review, edit, validate, and deploy — without letting AI modify protected core systems.

AI prompt Proposed blueprint diff Validation Developer approval Deploy
Typed APIs
Generate SDK types from your project model.
Permissioned by default
Every generated route runs through the permission engine.
Audit-ready
Track sensitive actions across users, workers, and integrations.
Runtime modes
Run APIs, workers, schedulers, and webhooks from the same binary.
OpenAPI-ready
Expose clear API specs for frontend teams and AI tools.
Modular architecture
Start as a modular runtime and split heavy services later.

Build the backend foundation once.

Create secure, generated, AI-ready backend systems for every app you launch.