Skip to content

Sylphx platform

Ship the whole backend with one command. Your agent can too.

Hosting, Postgres, Auth, AI and Sandboxes behind one key and one bill.

One account, one key
$ npm install -g @sylphx/cli$ sylphx login$ sylphx access projects create --spec.slug app✓ project app$ sylphx data databases create app-db✓ database app-db$ sylphx auth oauth-clients create✓ auth config app// the same three, from one keyconst sylphx = new Sylphx()const me = await sylphx.access.whoami({})await sylphx.data.databases.create({ parent: me.project!, databaseId: 'app-db' })

One account, one key, one bill.

1

One call

A project created over the API is unclaimed: an agent can make one with no account, and you take it over when you sign in. The CLI and the console make the same call.

bash
sylphx access projects create --spec.slug app
# unclaimed until you sign in

2

One key

One key per environment reaches every service you enabled, scoped to a role. Revoking it stops it everywhere within seconds.

bash
sylphx access api-keys create --spec.scopes data:read
export SYLPHX_API_KEY=sk_…

3

One bill

Every service meters into one invoice, line by line, at the prices published on this site — the same catalogue the console bills from.

bash
sylphx billing usage-reports list
# one line per product

An agent is a client, not a workaround.

One MCP server and one CLI, generated from the same API: an agent calls the same methods the SDK does, with the same key and the same permissions. The whole site is in llms.txt for a context window.

sylphx
{
  "mcpServers": {
    "sylphx": {
      "command": "npx",
      "args": ["-y", "@sylphx/mcp"],
      "env": { "SYLPHX_API_KEY": "sylphx_sk_…" }
    }
  }
}

// then the same action, as one call:
// sylphx_call { "method_id": "data.databases.list" }

Start with one call.