Watch an agent take an App from the first file to a live address. These are the calls it makes, and what every App comes with.
You
Make an applicant tracker for Acme: a form for candidates and a board for the team.
The App appears here
Each App has its own infrastructure so you can accomplish big things. Your agent controls it all over MCP or API.
Judt is fully headless, designed to be used by agents. Sure, you can use the dashboard too, but we don't expect you to.
Create, write, preview, publish and restore an earlier version. Connect with MCP, the API or the CLI.
Judt200 OK
{
"id": "dep_8Hq2…",
"status": "succeeded",
"published_at": "2026-10-28T09:22:41Z"
}If something fails, your agent gets the context to fix it. Query logs or events to see and fix issues.
The preview didn’t buildCould not resolve “hono/jsx” from src/index.tsx
422 Unprocessable Content
{
"error": {
"code": "preview_failed",
"message": "The App's dev server failed to build or start",
"detail": "Could not resolve \"hono/jsx\"…"
}
}Requests, console output and crashes, from the preview and the live App.
200 OK
{
"results": [{
"environment": "production",
"source": "app",
"level": "error",
"message": "ReferenceError: board is not defined"
}],
"has_more": false
}Clean and clear API for managing Apps. Judt is a fully headless platform, built for developers and agents.
curl https://api.judt.ai/api/apps \
-H "Authorization: Bearer $JUDT_TOKEN" \
-d '{"name": "Acme hiring"}'
200 OK
{
"id": "app_…",
"url": "https://acme-hiring.judt.dev"
}api.judt.aiAvailable
Add the MCP server to your agent and it gets the same tools our agent uses: write files, run commands, preview and publish. It even has logs to debug.
{
"mcpServers": {
"judt": {
"url": "https://api.judt.ai/mcp",
"headers": {
"Authorization": "Bearer ${JUDT_TOKEN}"
}
}
}
}api.judt.ai/mcp
Use Judt from any shell, you or your agent. Each command is one API call, and --help explains every one.
$ curl -fsSL https://judt.ai/install | sh
$ judt auth login
$ judt apps create --name "Acme hiring"
$ judt apps files write index.js --content @index.js
$ judt apps preview
$ judt apps deployjudtCLI docs
A template gives your agent an App that already runs. It spends its tokens on what makes your App different, not on sign-in pages and database setup.
A website for a café, with a menu, opening hours and a catering form.
Posts, search, cover images and feeds, with a Markdown editor.
Sign-up, workspaces, roles, invitations and a projects dashboard.
Channels with live messages, presence and typing.
A personal AI agent you can text on WhatsApp, iMessage or SMS.
A full-stack React App with server functions and a JSON API.
A JSON API with routes, middleware and error handling.
A single Worker that answers every request. For starting from nothing.
Durable Objects is the ideal infrastructure to build reliable, long lasting agents.
| Time | Agent | What woke it | What it did |
|---|---|---|---|
| 08:58 | Slack agent | “@agent the export button is broken” in #support | Opened SUP-142 in Jira |
| 08:58 | Slack agent | Same thread | Added the bug to the export runbook in Notion |
| 08:59 | Slack agent | Same thread | Replied with the ticket link |
| 09:00 | BI agent | Schedule: Mondays at 9:00 | Ran the week’s pipeline queries |
| 09:01 | BI agent | Same run | Updated the charts on acme-pipeline.judt.dev |
| 09:01 | BI agent | Same run | Posted the summary in #sales |
| 09:14 | Code review agent | Pull request #812 opened on GitHub | Read the diff, 214 lines |
| 09:15 | Code review agent | Same pull request | Left three comments on the lines |
| 09:20 | GTM agent | Northwind moved to Demo in the CRM | Built a showcase App from SaaS Starter |
| 09:22 | GTM agent | Same deal | Published northwind-demo.judt.dev |
| 09:22 | GTM agent | Same deal | Emailed the link to the rep |
| 10:03 | Code review agent | New push to #812 | Resolved two of its comments |
Each one is an App like any other, with its own code, database, Secrets and address. Your agent builds it with the same API.