Skip to content
Manybases

Edge functions

Server code, and no server.

One bundled module on its own subdomain, holding a secret key minted at deployment that never comes back — not to you, and not to the agent that wrote the code.

Read the docs
manybases functions deploy

One module, one subdomain.And two variables you never set yourself.

checkins.js
export default {
  async fetch(request, env) {
    const res = await fetch(`${env.MANYBASES_URL}/tables/checkins/rows?limit=200`, {
      headers: { Authorization: `Bearer ${env.MANYBASES_SECRET_KEY}` },
    });
    const { data, error } = await res.json();
    if (error) return Response.json({ error }, { status: res.status });
    return Response.json({ count: data.length });
  },
};

Both variables are injected at deployment. The secret key is the function’s own — minted when it ships, written into the script, and returned to nobody.

It has no direct handle on the database or the file store either: everything it reads travels over HTTP to its project’s API and passes through every check any other request passes through.

1 MB a module · 10 000 ms of CPU · 100 subrequests · not capped in number

The agent writes the code.The human types the value, and nobody reads it back.

Secrets are set once per project, from the dashboard, by a signed-in human. Every function of the project receives them within seconds — including the ones deployed later — and they survive redeployments.

Values are encrypted at rest, bound to the project and the name, so a value copied elsewhere does not decrypt. No route ever returns one. A human can read a digest, which is enough to check a paste and not enough to be a leak.

secretsset by a human
STRIPE_SECRET_KEYsha-256 3f9a…c17
RESEND_API_KEYsha-256 b204…8de

The agent sees the names. Never the values.

What it will not do.On purpose, and worth knowing before you build on it.

  • Execution output is not captured — not console.log, not a CPU overrun. What is captured is every request the function made to its project’s API.

  • No scheduled tasks and no incoming webhooks. A function answers a request; nothing wakes it up on a timer.

  • Nothing is uploaded from the dashboard. Your agent bundles the module and deploys it; the dashboard lists what it deployed.

Next.The parts this one leans on.

MCP

Thirty-seven tools for your agent

Got another idea?

Give it a backend.