The best launch is one nobody has to be awake for. Scheduled flags let you pick the moment a feature switches on, then go and enjoy your weekend.
Key takeaways
- Set a flag to switch on at a time you choose. No deploy, no rebuild.
- See every planned change on one timeline.
- Flag history shows who switched what, and when.
Launch without a keyboard
Deploy on Friday, set the flag to switch on at 9am on Monday, and close the laptop. When the time comes, the schedule flips the flag and the feature appears. Nothing is rebuilt and nothing is redeployed: the code was already live, it was just switched off.
Nothing changes over the weekend. The code is live, the feature isn’t.
Schedule your first flag
- Merge the feature behind a flag and ship it switched off.
- Open the flag in the dashboard and pick the environment.
- Set the time it should switch on, for example Monday at 09:00.
Tip: schedule production only. Leave staging switched on so the team can keep testing right up to the launch.
Every change, on the record
Scheduled or by hand, every switch lands in the flag history: who changed it, in which environment, and when. If something looks wrong on Monday morning, you don’t need a hotfix. One switch rolls it back.
Watch out: a schedule switches the flag on, it doesn’t check the feature works. Keep an eye on it after launch, even if nobody had to press the button.
Which plan has it
Scheduled flags, the timeline and flag history come with Full Mast.
| Feature | Flagpole | Full Mast |
|---|---|---|
| Scheduled flags | – | Yes |
| Schedule timeline | – | Yes |
| Flag history | – | Yes |
| Seats | 1 | 10 |
| Price | £0 | £30 a month per project |
Want to schedule your next launch? Request early access.