DooCloud

Starting a new backend always felt like losing 2-3 days before writing a single line of actual product logic. Docker setup. SSL. DNS. Auth. CRUD boilerplate. Same thing every time.

So I built DooCloud on top of Doolang — a compiled, type-safe language where your schema is your API definition.

Here is how it works:

You define a schema like this:

struct Task {
id: Int @primary @auto,
title: Str,
status: Int
}

DooCloud reads that and automatically generates:
sad

• Full REST API (GET, POST, PUT, DELETE)

• JWT auth with signup and login

• Rate limiting and CORS

• SSL and custom domain

• Postgres database

• Live logs and Git

You click Deploy. Your API is live. The whole thing takes under 5 minutes. I've timed it.

What makes it different from Railway, Render, Supabase

Railway and Render deploy your code. You still write everything. Supabase and Firebase give you a database with some helpers. You still write the API logic.

DooCloud generates the API and deploys it. There is nothing to write.

What is Doolang

Doolang is the language running underneath. Compiled, built on Rust and LLVM. It hits 1.38M RPS on plain text and 1.27M on JSON. Fully open source: github.com/nynrathod/doolang

Try it without signup

The playground at doocloud.dev#playground lets you define structs and see the generated API endpoints in real time. No account needed.

Try the playground here: doocloud.dev/#playground - define a struct, watch the API generate live.