Skip to main content
Judt is a platform where you and your agents create, test, and publish full-stack web Apps without managing infrastructure. Each App has a development sandbox, a Git repository, a build and deployment pipeline, and an isolated production runtime. Documentation is split into two main sections:
  1. Managing Apps: Everything related to creating, editing, and deploying Apps. Think the infra around it.
  2. Building Apps: Direct features of the Workers style environment (Javascript runtime, Durable Objects, D1 SQLite, etc..).

Building Apps:

Every Judt App runs on celld, a Workers-compatible JavaScript and TypeScript runtime. An App can configure its own resources in wrangler.json:

Manage Apps

You can manage Apps through four interfaces or in the Judt dashboard. All four interfaces share the same permissions, validation rules, and state.

How an App works

An App moves from source code to production in five steps:
  1. Create the App. Start from a template. Judt gives the App a unique slug and a production URL at https://<slug>.judt.dev. See Apps and addresses.
  2. Edit and test in the sandbox. Each App has a Linux sandbox with a /app working directory, Git repository, shell command runner, and live dev server. The sandbox starts automatically when a request needs it and stops when idle. See Sandboxes.
  3. Set Secrets. Store API keys and credentials outside your source files. Judt gives Secrets to the sandbox dev server and to production deployments as properties on env. See Secrets.
  4. Commit and publish. Save your sandbox changes as a Git commit with a durable backup, and then deploy that commit to production. See Commits and deployments.
  5. Control access and monitor. Share preview links to the sandbox, set production visibility (public, password, or private), and inspect platform events and runtime logs. See Previews and access and Troubleshoot an App

Get started

Quickstart

Create an API key, create an App, change a file, and publish it from your terminal.

Authentication

Authenticate requests with an API key or an OAuth access token.

Give an agent access

Connect an external agent with an App token or OAuth sign-in.

Build Apps

Learn how to write Worker handlers, configure bindings in wrangler.json, and use storage.