Zeus · A coder in your pocket

POCKET IDE

The engineer who’s always in your pocket—plain language, real runs, the same help on laptop and phone

Studio · live bar · MCP in Cursor — one subscription, one “coder”

Zeus (Pocket IDE) is not a narrow database panel—it’s a pocket developer: you describe what you need, it executes through a real control plane (migrations, health, growth, backups, the operational junk you’d ping a staff engineer for). Add /pocket on your home screen and the same product meets you on the go.

The ambition: automate as much of your life as you choose to wire in—work, side channels, the recurring noise. One pocket, your guardrails, your skills. Not magic; a system you can keep tightening until it really runs the stack you care about.

Start with Hero — $29/mo Compare Plans View MCP SetupMolt host not set

Live line uses /api/molt/studio → configure MOLT_API_BASE (override in .dev.vars for sandboxes).

A coder in your pocket—not a second monitoring tab.

Zeus is the thing you open when you’d rather talk than hunt through consoles: migrations, health, what’s on fire, and recovery paths—driven from a studio that fits your phone, your browser, and your IDE. The infrastructure underneath is real; the story we sell is a companion, not config hell.

One brain, every surface: web · MCP · mobile.

Same subscription: a live query bar, demos for quick context, and Model Context Protocol in Cursor so you don’t re-learn a different product per screen. The pocket is the product—the transport is your choice.

Serious work gets backups, not vibes.

Encrypted retention and restore, tiered to how much pain you can afford. Coders in pockets still need audit trails and rollback when production disagrees with the plan.

Built to grow with what you ship.

Multi-tenant, scoped credentials, and namespaced storage so we can add capabilities without turning your account into a science fair. Start with the jobs that hurt today; the platform stretches with the next one.

Not just your repo—room to automate a whole life.

Same pocket can touch work, side projects, and the other systems you wire in: heartbeats, skills, messaging, the boring recurring stuff that eats your week. The ceiling is your appetite to connect and your rules—Zeus is the lever, not a mind reader. You decide what “whole life” means; we give the automation muscle.

See Pocket IDE in action

Demos for taste; sign in for the real pocket—live calls into health, growth, and migration state, the way you’d nudge a teammate who actually owns prod.

⚡

Pocket Studio

Demo below · Live bar calls Molt through Pantokrator (sign-in required)

Pocket

Welcome to Pocket Studio—your Zeus “coder in the room.” Try a demo, or sign in and use the live bar: we route your questions to the Molt control plane at your Molt control plane (migrations, health, growth, backups).

Live Molt (from your pocket)

🔒 Demo chips are simulated · Live bar needs MOLT_API_BASE + MOLT_API_TOKEN on this WorkerTry Pocket IDE free on any tier

Choose Your Ascension

Three tiers · Cancel any time · No data held hostage

Mortal

$0/ month

The coder in your pocket—on the house.

✓Pocket studio + Molt: talk to a real control plane, not a toy chat
✓MCP so Cursor can drive the same runs you see in the browser
✓Weekly automated backups; 7-day retention on the free tier
✓Community support

Start Free

Use Pocket IDE from Cursor, Claude, or any MCP client

One MCP server: your pocket coder in Cursor, same brain as the web studio · Zero extra context to lug around

Add to your MCP config

{
  "mcpServers": {
    "pocket-ide": {
      "url": "https://mcp.pantokratorai.com/pocket-ide",
      "apiKey": "pi_your_api_key_here"
    }
  }
}

@pocket migrateApply a schema or migration your environments expect—no copy-paste from docs.

@pocket backupSnapshot state to durable storage so rollback isn’t a fantasy.

@pocket restoreBring an environment back from a known backup id—ask your pocket, not a runbook.

@pocket analyzeGet AI help reading structure and risk before you change production.

@pocket statusHealth, drift, and “are we good?” in one call from the IDE.

@pocket list_backupsEnumerate what you can still trust when things go sideways.

@pocket migration_statusHistory of what shipped, when, and in what order—so blame is boring.

Multi-tenant by design, built to grow

Zeus is built as a platform: every customer gets an isolated home so the pocket coder can grow new skills without you rebuilding trust from scratch. Same boundaries as we wire more of your stack into the same conversation.

Isolation #1

Per-tenant tokens

Each tenant’s provider credentials are stored with strict separation. Zeus resolves them at request time—never a shared “god key” in a spreadsheet.

Isolation #2

Tenant-scoped queries

Every control-plane statement includes tenant_id = ? — enforced at the API boundary, not just the ORM layer.

Isolation #3

Namespaced artifacts

Backups and snapshots live under tenant-scoped prefixes—no cross-tenant reads. Your pocket coder only sees what your org is allowed to touch.

Put a coder in your pocket

Start on Mortal, upgrade when the pocket needs to work harder for the team. Cancel any time. You keep ownership of the systems—Zeus is the layer that makes talking to them feel like having a staff engineer on speed dial.

Ascend to Hero Browse MCP Marketplace