You have bought Lasersite. You now hold two things: a licence key, and the right to pull the software from our release registry. This page takes you from there to a site that is live on your own domain.
Budget about 30 minutes. Nothing here needs prior server experience, but you will use a terminal.
What you need first
- Your licence key — in your confirmation email and in your account. - A place to run it. Fly.io, Railway and Render all work. You need two things there: an app and a Postgres database. - A domain you control.
1. Sign in to the registry
Your licence is what unlocks the download. Nothing is checked inside the software itself, so this is the only place the key is used:
docker login registry.lasersite.ai -u YOUR@EMAIL -p YOUR-LICENCE-KEYIf your platform pulls the image for you, put those same credentials in its registry settings instead.
2. Create the database FIRST
The app runs migrations when it starts, so the database has to exist before the first boot. On Fly:
fly postgres create --name my-db --vm-memory 1024
fly postgres attach my-dbGive it 1 GB. --vm-size shared-cpu-1x sets CPU, not memory — memory still defaults to 256 MB, and Postgres is killed in a loop under it. The symptom is confusing: the app reports "connection timeout" and the database machine looks healthy.
3. Set one secret and deploy
fly secrets set AUTH_SECRET="$(openssl rand -base64 32)"
fly deployAUTH_SECRET is the only value you must set. Everything else — including the key that encrypts your stored Stripe and email credentials — is derived from it. Keep it safe; changing it later makes those stored credentials unreadable.
4. Run the setup wizard
Open your new site. You will land on /setup, which asks for your business name, your name, your email and a password. That creates your admin account and your site in one step, and the page disappears afterwards.
You do not enter your licence key here. The software never contacts us — the licence did its job at step 1.
5. Point your domain
Add your domain in your platform, create the DNS records it gives you, and wait for the certificate. On Cloudflare, keep the records DNS-only (grey cloud) until the certificate issues, or the validation cannot reach your server.
After that
Everything else is done inside the admin: pages, theme, products, checkout, email, automations. Those live in your database, so **updates never overwrite them.**
When a new version is released your instance tells you, and you choose when to take it. If your update subscription lapses, nothing stops — you simply stop receiving new versions until you renew.
If you get stuck
Reply to your order confirmation. It reaches a person.
Comments