The runtime for AI-built projects

That feels backwards

Putting that software online still means thinking about hosting, backends, databases, servers, configuration, and infrastructure you may have to maintain long after you stop caring about the project.

The idea

We built Day Zero around a simple idea:

If software is becoming disposable, the runtime should be disposable too.

For the little things

Day Zero is for the little things you build with Claude, Codex, Cursor, or your favorite coding agent:

• the prototype you’re not sure anyone wants
• the tool five coworkers need
• the voting app for this weekend
• the dashboard you’ll use twice
• the weird idea you made at 2am

Most of these things don’t need a “stack.”

They need a runtime: data management, user management, access control, and somewhere for the app to run.

A runtime for AI

Day Zero is the runtime for AI-built software. It includes data tables for data management, user management for who belongs to the project, access control for public or private sharing, and the runtime that keeps the app live.

The app reads and writes data tables through our JavaScript library. Access control is public, or private with a simple access code.

We’re deliberately keeping that model small. The goal isn’t to recreate AWS, Vercel, or Supabase with fewer buttons.

The goal is to remove infrastructure decisions entirely.

Small enough for agents

Because the platform is small, coding agents can understand and operate it too. Give your agent our ai.md, and it can learn how Day Zero works and deploy your project.

Our philosophy

Build it. Put it on the runtime. See if anyone cares.

If it succeeds, great.

If it doesn’t, throw it away.

Small software should have a small runtime.

That’s Day Zero.