ASTRODOCK Features Sign-inAccounts and passkeys, no password in your app Databases & storageIts own Postgres and bucket, or yours Deploys & runtimesPush, upload, or let an agent do it Secrets & configNames in the repo, values on the platform Domains & HTTPSSubdomains and certificates, handled Monitoring & backupsLogs, alerts and nightly dumps For agents Self-hosting Docs Install

Features · Sign-in

Your app never sees
a password.

User accounts are the reason small tools stay on localhost. Astrodock does them once, for everything you deploy.

a person Astrodock password stops here your app signs in one-time code

How it works

01

You send them away

Your app redirects to the platform's own address. Whatever happens there is not your code's problem.

02

The platform asks

Password, passkey, second factor — whichever you've turned on. It also checks they're allowed into this particular app.

03

You get a code, not a credential

They come back with a one-time code. Your server trades it for their identity and starts a session of your own design.

Why it matters

The riskiest code
is the code you skip.

Hand-rolled auth is where small projects get hurt: a password logged by accident, a reset flow nobody tested, a session that never expires. None of that exists here, because none of it is in your app.

It also means the tool you wrote in an afternoon can have passkeys and two-factor — things you would never have built for it — because they belong to the platform.

One session, every app Sign in once, reach everything you're granted
Access per app The rota tool, but not payroll
Or none at all A landing page doesn't need a login

Give it a machine
and ten minutes.