for developers

Write it. Ship it. gl hf.

Tools in TypeScript, tested locally, deployed with one command. Every agent in the company can call them a minute later.

curl -fsSL https://zya.dev | bash

Three commands from function to tool. Run it against your local source, deploy it, and call the live copy.

Tools are TypeScript. A schema built with @zenitya/sdk, MCP hints, and an execute function. Every property is required and unknown ones are rejected, so a model can't guess its way past the input.

order-tools/src/index.ts

import { Project } from "@zenitya/sdk";
import { s } from "@zenitya/sdk/schema";
import { orders } from "./orders";

const project = new Project();
export default project;

project.tool("searchOrders", {
  title: "Search orders",
  description: "Finds orders by status, newest first.",
  schema: s.object({
    status: s.enum("open", "late", "refunded"),
    limit: s.integer().describe("1 to 50."),
  }),
  outputSchema: s.array(
    s.object({ id: s.string(), total: s.number() }),
  ),
  hints: { readOnlyHint: true },
  execute: async ({ status, limit }) =>
    orders.search(status, limit),
});

project.tool("refundOrder", {
  title: "Refund order",
  description: "Refunds one order in full.",
  schema: s.object({
    id: s.string(),
    reason: s.string().nullable(),
  }),
  outputSchema: s.object({ refundId: s.string() }),
  hints: { destructiveHint: true },
  execute: async ({ id, reason }, ctx) => {
    ctx.logger.info({ id }, "Refunding order.");
    return orders.refund(id, reason);
  },
});

Every repo is a project. Keep billing tools with billing code and order tools with order code. Each project deploys on its own, and every one of them lands in the same pool.

Builds you don't have to trust your laptop for. zya deploy uploads source, never a build. Install can only reach the npm registry, bundling runs with the network off, and the live version only changes when everything passes.

app.zenitya.com/acme-labs/projects/order-tools/builds/8f3a21c

Build 8f3a21c

order-tools · 41s · ci-deploy

Upload48 KB of source, checked against its hash.0s

InstallFresh VM. Reaches registry.npmjs.org, nothing else.14s

BundleSecond VM with the network off.9s

Describe6 tools found, schemas validated.3s

ActivateReplaces 71d4f0a in one step.1s

Run tools where your data lives. Tools run in our managed sandboxes by default. Point a project at a runner on your own VPS, in a GCP VPC, or behind WireGuard or Tailscale, and its tools reach private databases with that machine's credentials.

app.zenitya.com/acme-labs/projects/billing/settings

billing · Runtime

Where this project's tools run. Switching doesn't rebuild.

Zenitya cloudManaged sandbox per callonline

warehouse-vpcRunner · GCP VPC, europe-west1online

office-tailscaleRunner · Tailscaleonline

legacy-dbRunner · WireGuardoffline

Runners dial out to Zenitya. Nothing listens on your network.

$ zya runner start --name warehouse-vpc

Code mode, for agents that think in code. The pool is served as one tool with a typed API. The model writes a short script, it runs next to your tools, and only the result comes back.

run · code mode

const late = await tools.searchOrders({ status: "late", limit: 50 });

const small = late.filter((order) => order.total < 40);
for (const order of small) {
  await tools.refundOrder({ id: order.id, reason: "Shipped late" });
}

return { checked: late.length, refunded: small.length };

← {"checked":50,"refunded":11} · 1 round trip

Bring the tool you keep rewriting.

A small private beta. Bring one tool and the agents that should call it; we build the rest with you.

Request private beta access