Developers

One small cloud a coding agent can build against.

A compact TypeScript contract for deploying web, data, auth, files, workers, and operational agents as one app.

$npx tarantula new renewal-board↵

renewal-board/proposed alpha API

app/↳ page.tsx↳ styles.cssworkers.tstarantula.ts

import {
  defineApp, web, database,
  auth, storage
} from "tarantula";

export default defineApp({
  web: web("./app"),
  database: database({ accounts }),
  auth: auth({ audience: "workspace" }),
  storage: storage(),
  workers: [syncHubspot],
  agents: [reviewRenewals],
  connections: [hubspot]
});

local cloud readylocalhost:3000

Two kinds of agents. One clear boundary.

BUILD TIME

Coding agent

Reads the repo and Tarantula contract, writes the app, runs the CLI, and proposes the deployment.

RUN TIME

Operational agent

Runs inside the deployed app from a user action, webhook, or schedule, with scoped tools, checkpoints, budgets, and approvals.

agent({
  on: schedule("0 8 * * 1"),
  tools: [accounts, hubspot],
  budget: "$2/run",
  approve: ["outreach.send"],
  run: reviewRenewals
})

Three commands

A complete loop with almost nothing to remember.

Create

$ npx tarantula new my-app

Start from a small full-stack app your coding agent can read in one pass.

Develop

$ npx tarantula dev

Run the web app, database, auth, workers, files, and agents together locally.

Deploy

$ npx tarantula deploy

Publish the exact app you tested and receive a shareable URL.

The cloud API

Literal primitives. One shared context.

Agents do not need to discover which vendor, SDK, credential, and dashboard own each part of the app.

PrimitiveIn codeRuntime context

Launchpadweb()request · env · logs Loopagent()run · tools · approval Sparkworker()event · queue · schedule Tablesdatabase()query · mutation · transaction Doorauth()user · team · role Librarystorage()object · upload · signedUrl Switchboardconnection()grant · actor · audit

Built for coding agents to inspect

Let coding agents inspect state instead of scraping dashboards.

The CLI exposes schemas, rows, files, permissions, worker logs, agent traces, usage, and deployment state in predictable formats. JSON output is versioned, resource IDs are stable, and failures return non-zero exit codes.

terminalnpx tarantula inspect --json

$ npx tarantula inspect --json

APP       renewal-board
URL       renewal-board.tarantula.app
ACCESS    workspace · 8 users

DATABASE  healthy · 42 rows
WORKERS   3 active · 0 failed
AGENTS    1 running · 14 complete
STORAGE   18 objects · 24.6 MB
SECRETS   2 grants · 0 raw keys

✓ production matches local contract

The contract

Local mirrors production

The same bindings, schema, and permission contract exist before deploy.

App resources are code

App-owned resources are versioned beside the code; company credentials stay in the vault by connection name.

Deployment plans are explicit

One plan previews code, migration, worker, agent, and policy changes and reports what applied.

The surface stays small

Tarantula adds integrated capability before it adds another concept.

Private alpha

Give your coding agent a smaller cloud to understand.

Request access Read the security model