What a Backend Project is

A Backend Project is DontCode with your own code in front. You write the app and host it wherever you like; the project supplies the services behind it.

What the project runs

• Auth: signup, login, email verification, MFA, social login, sessions, and the users table.
• Database: an isolated PostgreSQL schema, changed through migrations.
• Storage: a public and a private bucket.
• Payments: KakaoPay, NaverPay, Toss, PayPal, plus plans, features, and entitlement checks.
• Key-value store and realtime for shared state and live updates.
• Email for verification codes, receipts, and notices.

What stays yours

The repository, the framework, the hosting, the pages, and the session cookie. DontCode never deploys a Backend Project; it answers its requests.

How the two meet

Everything goes over HTTPS to the v1 gateway at backend.dontcode.co, authenticated with a project API key in the Authorization header. The dontcode npm package is a typed wrapper over the same routes, so you can start with the SDK and drop to raw HTTP any time.

The console still matters. Users, Database, Files, App Income, and Usage all show the same data your code writes, and settings such as signup rules and social login providers are set there, not in code.

Where DontCode fits

Pick a Backend Project when you already have code or a stack you want to keep. Pick an Insight Project when you want DontCode to write and deploy the app too. Both kinds get the same services; only who owns the code differs.