Getting started

You've bought Lasersite — what now

From licence key to a live site on your own domain, in about 30 minutes.

Created 9 Aug 2026Updated 22 Aug 2026

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 key is the password to the release registry. Your username is the email you bought with.

docker login registry.lasersite.ai -u YOUR@EMAIL -p YOUR-LICENCE-KEY

The image is registry.lasersite.ai/app:<version>. For <version>, take the newest entry from the release manifest — and pin it rather than following a moving tag, so nothing changes underneath you overnight.

If your platform pulls the image for you, put the same two values in its registry settings instead. On Render that is Workspace Settings → Registry Credentials, and the credential has to be named exactly lasersite.

2. Create the database FIRST

The app runs migrations when it starts, so the database has to exist before the first boot. On Fly, create the app first — without it there is nothing for the later commands to act on:

fly launch --no-deploy
fly postgres create --name my-db --vm-memory 1024
fly postgres attach my-db

Give 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)"

On Fly, one step comes before the deploy. Fly does not store credentials for an outside registry, so the image has to be copied into Fly's own registry first. The helper script does the copy and the deploy together:

brew install crane
scripts/update-fly.sh --app YOUR-APP

On Render and Railway there is no copy step — they pull the image directly with the credentials you stored.

AUTH_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. It was used at step 1, to fetch the image.

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.

Was this helpful?

Comments

You've bought Lasersite — what now | lasersite.ai