Manage
Account management
Your Hatchik account lives at hatchik.com/account. Sign in with the email you signed up with — we'll send a one-time link, no password.
The two logins (important)
This trips up almost everyone on day one. Hatchik has two completely separate sign-in surfaces, and they have nothing to do with each other.
Your Hatchik account
Lives at hatchik.com/account. The email here is your email as a Hatchik customer. It controls billing, sandbox lifecycle, GitHub connection, and account details. There's one of these per founder.
Your end-users' login
Lives inside your sandbox at yoursubdomain.hatchik.com. The accounts here are your customers' accounts — the people using the app you're building. There can be thousands of these.
A useful mental model: surface 1 is "Hatchik's customer table" (you and other founders). Surface 2 is "your customer table" (your end-users). The two never talk to each other directly. You don't sign in to your own sandbox as the owner via surface 2 — when you click your sandbox magic link, you're going in as the owner-user record we provisioned for you, which is part of surface 2 but happens to be you.
Tip. If you ever get confused, the rule of thumb is: hatchik.com/... means surface 1; yoursubdomain.hatchik.com/... means surface 2.
Signing in
Head to hatchik.com/account, type your email, and we'll send a sign-in link. The link expires in 30 minutes and is single-use. If you've lost the email, just request another.
Updating your name
Settings tab → First name. Used when we greet you in emails. Saved instantly.
Email is read-only — changing it would mean moving your sandbox to a new owner record. If you need to change the email on file, email hello@hatchik.com and we'll migrate it for you.
Connecting GitHub
Settings tab → Connect GitHub. Enter your GitHub username (without the @) and we'll add you as a collaborator on the sandbox repo we created for you. From that moment, you can clone the repo to your laptop and push to it.
You can leave this blank if you'd rather not connect GitHub — we'll keep the repo under our org and email you a link. You can still push if we add you as an outside collaborator. Most people just give us the username at signup; it takes seconds.
Signing out
"Sign out" link in the header. That ends your Hatchik account session (surface 1). Your sandbox session (surface 2) is independent — you'd need to sign out separately from inside the sandbox if you wanted to clear that one.
Pausing, archiving and restoring
Hatchik does no manual pause/resume. Instead, the lifecycle is automatic:
- Active — running normally. The default state for everything.
- Archived — if a Sandbox-tier sandbox has had no traffic and no commits for 30 days, we archive it. The Docker stack is stopped and the volumes are tarred up, freeing host resources. You'll get an email a few days before this happens so you can keep it active by pushing a commit or hitting the URL.
- Deleted — after another 7 days in archived state with no restore request, the archive is purged.
To restore an archived sandbox, head to hatchik.com/restore-sandbox, sign in with your email, and click "Restore". The sandbox is unpacked, started, and brought back to its previous URL within a couple of minutes. All your data, code, and customers are intact — archiving doesn't lose anything, only frees a server while you're not using it.
Launch tier sandboxes are never auto-archived. Only the free Sandbox tier follows the 30-day idle rule. Paid sandboxes stay running until you tell us otherwise.
Deleting your sandbox
Danger tab → Start deletion, or go directly to hatchik.com/delete-sandbox. We send a confirmation email; nothing is removed until you click the link in that email. Once confirmed:
- The tenant Docker stack is stopped and removed.
- The sandbox subdomain becomes available again to other users.
- Your Postgres volume, file storage and config are wiped after a 14-day grace period (during which you can email us and we'll restore from backup).
- Your GitHub repo is not touched. It's yours; you can keep it, delete it, archive it.
Billing
Billing tab → manage invoices, payment methods, and subscription. Payment processing runs through Paddle, our Merchant of Record, so the "Manage subscription" link opens Paddle's customer portal in a new tab.
For invoices, refund requests or billing questions, contact hello@hatchik.com and we'll handle it (we work with Paddle on the back end, you only talk to us).
Getting your data out
Email hello@hatchik.com with the subject "Data export". We'll send you a Postgres dump (.sql.gz) of your sandbox database within one working day, free of charge, any time you want one. No exit fee, no extraction fee. Your code is already on GitHub under your account. Your customers' data is yours.
Next
- What's included — the Sandbox-vs-Launch boundary.
- FAQ — common questions about ownership, exit and data.