Click → URL
Pick a template from the catalog. Click create. Get a dedicated subdomain that proxies to your Machine via authenticated edge.
PRODUCT
Gentity. Give every AI agent its own machine.
Gentity spins up isolated AI agent instances on Fly Machines — each with its own URL, its own state, and its own runtime. Pick a template, click create, open the link.
~/gentity
$ gentity create --template openclaw→ Spawning Fly Machine in iad …→ Mounting Volume agent-oc-x7k2 …→ Reverse proxy ready✓ https://oc-x7k2.gentity.app
WHAT IT IS
An agent, an isolated box, a URL.
Every Gentity instance is its own Firecracker microVM with a mounted Volume. Auth lives in front. State lives in back. You get a link.
Persistent state
Each instance has its own Fly Volume. Restart, stop, resume — agent memory, files, and config survive.
Cold start in seconds
Fly Machines boot Firecracker microVMs in under a second. Sleep when idle, wake on request. Pay for what runs.
HOW IT WORKS
Four steps. Nothing else.
No Docker Compose, no Kubernetes, no reverse proxy to babysit. Gentity composes Fly Machines, Volumes, and the edge proxy for you.
- 01
Sign in with GitHub
Allowlist-gated OAuth. Cookies are scoped to your subdomain tree so every agent inherits auth.
- 02
Pick a template
Choose an agent image and resource shape. Templates are typed: image, internal port, data path, env schema.
- 03
Click create
Gentity provisions a Fly Machine plus a Volume, persists the encrypted env, and registers the subdomain.
- 04
Open the URL
Hit <id>.gentity.app. The control plane authenticates the request and proxies through Fly's internal DNS to your Machine.
USE CASES
What teams put on Gentity.
Per-user agent sandboxes
Give every customer or every internal user their own agent box. State and credentials stay isolated; auth lives at the edge.
Long-running task agents
Spin up a Machine for an agent that crawls, watches a repo, or runs a multi-hour workflow. Pause and resume without losing state.
Self-hosted MCP / tool servers
Run an MCP or tool server per workspace. Gentity gives each one a dedicated subdomain, persistent volume, and access control.
BUILT ON
Fly Machines
Firecracker microVMs, sub-second cold start
Fly Volumes
Persistent storage per agent
Next.js 16
Control plane + edge proxy
Auth.js
GitHub OAuth + allowlist
Prisma + Neon
Postgres for instance state
AES-256-GCM
Encrypted env per instance
WHAT YOU GET
Sensible defaults, no Kubernetes.
- Firecracker microVM isolation per instance
- Encrypted env vars at rest (AES-256-GCM)
- Allowlist-gated GitHub OAuth at the edge
- Persistent Fly Volume per agent
- Sub-second cold start, sleep when idle
- Open source — fork or self-host the control plane
READY?