About Deloc

Claude Code and Cursor can write software in minutes. Publishing it to a URL still takes an afternoon. That gap is what we're closing.

What we're building

Deloc turns anything you build on your machine into a shareable URL in one command. Say "deploy this to Deloc" in your AI coding tool, or run npx @deloc/cli deploy from any terminal. No DNS, no build YAML, no auth code, no infrastructure to keep alive after the app ships.

And when those apps need to call an API — Stripe, OpenAI, an internal service — Deloc lets them, without ever exposing credentials to the browser.

The problems we're solving

The gap between "I built it" and "they can see it."

AI coding tools compressed "idea to working prototype" from weeks to minutes. Publishing that prototype to something a coworker can open still means buying a domain, configuring DNS, writing deploy YAML, and debugging CI. The productivity you gained in the editor is bottlenecked at the deploy step.

Governance in the age of AI-built tools.

Every company now has employees shipping internal apps with Claude, Cursor, and v0. IT teams see two options: ban the tools (and kill the productivity gains) or allow them (and lose all visibility). There's a third option — let people ship, but enforce SSO, email-domain restriction, and audit logs at the edge. Admins keep control without becoming a deploy pipeline.

Auth is infrastructure, not product.

Publishers shouldn't write login code to share a dashboard with their team. Authentication should live at the CDN, before a single byte of the app reaches the browser. Password pages, screenshots pasted into Slack, and leaked share links are symptoms of a tooling gap, not user error.

Pricing that doesn't punish teams.

Per-seat pricing turns ten internal-tool builders into a budget line item and stalls adoption inside the companies that need it most. The people reading dashboards — the viewers — should be free. Only publishers need a seat.

What we believe

Publish from where you build. The CLI and MCP server are the product, not the dashboard. The dashboard exists for management and governance, not as the primary way to ship.

Static is a security feature. No server-side execution means no server-side exploit. When a dynamic call is needed, it goes through a narrow, audited, credential-isolated proxy — not a server the publisher has to maintain.

Viewers are always free. The value of an internal tool scales with how many people can see it. Charging per viewer is charging against the product working.