Jetstack
For developers and partners

Build production apps without owning the infra.

A secure backend you don't have to build. REST, webhooks, queues, search, signed file URLs, AI, and a built-in MCP server — already there.

What you can skip building

The secure backend layer is done.

All the boring (and risky) parts of running a real app — already in. Use them; don't rebuild them.

  • Hosting & scaling

    AWS-backed runtime. Tier-based scaling. Zero-config deploys.

  • Queues & async

    Durable job queues. Backoff. Dead-letter visibility.

  • File repository

    Native files with transforms and streaming.

  • Signed file URLs

    Time-bounded, tamper-proof access to private files.

  • Full-text search

    Fast, indexed search across your application data.

  • Audit log

    Configurable activity log for compliance.

  • Push & SSE

    Mobile push and SSE for terminal subscriptions.

  • Scheduling

    Cron-like and one-shot event scheduling.

  • Rate-limited REST

    Per-key, per-route limits. Out of the box.

  • Webhooks

    Outbound events with signing, retries, and delivery logs.

  • MCP server

    Talk to your data from Claude, Cursor, or any MCP environment.

  • AI orchestration

    AI agents wired to platform tools.

Your data, native to AI.

Query records and trigger actions from Claude, Cursor, or any AI agent — through a built-in MCP server, governed by the same permissions as everything else.

tool_call jetstack.query
{ "type": "orders", "since": "7d" }
200permission-scoped
What stays in your hands

The product is still yours to build.

Where engineering judgment matters — model design, workflows, integrations — you stay in control.

Data model

Object types, properties, constraints, calculations. Yours to design.

Automations

Workflows, triggers, custom actions. Code or no-code.

Custom canvases

Page composition with blocks or custom HTML.

Integrations

External service glue, webhooks, third-party APIs.

Two tracks

Implementers and integrators.

Most teams use both. Start where your work lives.

Track 01

Implementers

Platform foundations: model design, views, canvases, automations, public pages, custom forms.

  • Application modules and data model paradigm
  • Object types, properties, and data views
  • Automations, triggers, and workflows
  • Public pages and custom forms
View implementers docs ↗
Track 02

Integrators

A built-in MCP server for talking to your data from any AI environment. REST API, webhook patterns, service-to-service connectivity, and event-driven integrations.

  • MCP server — talk to data from Claude, Cursor, IDEs
  • REST API architecture overview
  • API-based interaction with model entities
  • Webhook-driven event handling
  • Service-to-service connectivity
Open API reference ↗
Developer experience

A real REST API. Real webhooks. A real MCP server.

Predictable, rate-limited, and reflective of your model — talk to your data from the AI environment you already use. The shapes below are illustrative.

// Create a record
const res = await fetch(`${BASE_URL}/collection/customers`, {
  method: "POST",
  headers: {
    "x-api-key": process.env.TOKEN,
    "content-type": "application/json",
  },
  body: JSON.stringify({ name: "John", surname: "Doe" }),
});
// Send a webhook event
await fetch(`${BASE_URL}/webhook/push-event`, {
  method: "POST",
  headers: {
    "x-api-key": process.env.TOKEN,
    "content-type": "application/json",
  },
  body: JSON.stringify({
    event: "customer.updated",
    occurred_at: new Date().toISOString(),
    data: { id: "cus_8h2", active: true },
  }),
});
// Subscribe to an SSE channel
const events = new EventSource(
  "https://sse.jetstack.dev/you-app/subscribe/event",
  { headers: { "x-api-key": process.env.TOKEN } }
);

events.onmessage = (e) => {
  console.log(JSON.parse(e.data));
};
Onboarding sequence

The fastest path to your first shipped app.

step 01

Understand the model

Build a pilot module — objects, permissions, key views — to internalize the patterns.

step 02

Add process logic

Introduce automations, button actions, and event hooks around real workflow states.

step 03

Integrate and ship

Wire external services via REST and webhooks. Validate UAT. Deploy.

For partners

How to position Jetstack to your clients.

When clients ask "why not just AI app generation tools or self-hosted?" — these are the answers that hold up.

Prototype speed without production volatility

Prompt-first tools accelerate concept work, but production apps need deterministic behavior. On Jetstack, changes are intentional and reviewable.

No infrastructure burden

Your client does not own deployment, scaling, monitoring, or audit infrastructure. That category of cost and risk simply moves off the table.

Clear story from request to feature

Model, workflow, and UI changes are explicit and reproducible. Scope and acceptance criteria stay grounded.

Long-term delivery confidence

Ship quickly while preserving the consistency, governance, and ownership stability that serious business systems require.

Become an implementation partner.

Share your team profile and target use cases. We'll plan onboarding and cooperation.

Open docs map