How To
Start with a Layover
Get a temporary managed server in one click to try strackt before you bring your own — and how to keep it or move on.
Start with a Layover
A Layover is a temporary managed server strackt runs for you, so you can get an app live without bringing your own server first. It's a place to start, not a place to stay — you have 30 days to move to a server of your own.
Starting one
In the Add Server flow, choose Start a Layover. You'll see a short summary of what
you get, and one click sets it up — no cloud account, no VPS, nothing to configure.
strackt provisions the server, and your first app is reachable at a strackt address
ending in .layover.on-strackt.dev. Its overview page shows the live link and how
much time is left.
A team can run one Layover at a time. It's meant for trying things out, so it runs a single application across up to three environments.
The 30-day clock
A Layover lasts 30 days from when you start it. strackt reminds you as the end approaches — around three weeks in, then again in the final days — so it never expires on you by surprise.
When the 30 days are up, your app keeps running. What changes is that you can no longer deploy new changes to it until you do one of two things:
- Move it to your own server (recommended), or
- Keep the Layover for €10/month.
If you take neither and leave it, the Layover is eventually cleaned up about a week after it ends — so don't leave anything on it you want to keep past then.
Moving to your own server
This is the intended next step. On the Layover's overview, Move to your own server lets you pick a server you've connected and moves your environment onto it — your data comes across and there's only a brief switch-over. See Move an environment to another server for how a move works. Once everything has moved off, strackt tidies the Layover away for you.
Keeping the Layover
If you'd rather keep running on the Layover for now, Keep it running — €10/month turns it into a paid server and stops the clock. This is a separate subscription from your apps — keeping a Layover never affects billing for anything else on your team. If you cancel it later, the 30-day clock simply starts again from that point.
Good to know
- The Layover is reachable through a strackt address, so you don't set up DNS for it — custom domains are something you add once you're on your own server.
- The clock is calendar time: a Layover reaches 30 days whether or not you deployed to it, so start it when you're ready to use it.
Was this helpful?