What happens after the 14-day trial?

You automatically drop to the free plan — no charge, no interruption. You keep all your tasks and data forever. No credit card required to start.

Does Flowly sync with Google Calendar?

Yes. Pro plan includes two-way Google Calendar sync. Events appear as tasks, and Flowly tasks show up in your calendar so your schedule stays in one place.

Can I export my data?

Always. Export all tasks, time logs, and analytics as CSV or JSON from your account settings at any time — your data is yours.

How is Flowly different from using Toggl + Todoist?

Flowly tracks time inside the task — no tab switching, no import/export, no double-entry. One click starts the timer; one click marks done. Everything lives in the same view.

What happens if I cancel Pro?

You drop to the free tier immediately with no data loss. Tasks beyond the free limit are archived (not deleted) and restored automatically if you resubscribe.

Why freeze the release branch?

A branch freeze stops new, unreviewed changes from slipping into a release while it is being tested. Without it, you can never be sure the build you tested is the build you are shipping.

Why prepare rollback steps before deploying?

If something breaks in production, you want recovery to be a known, quick procedure rather than something you figure out under pressure. Writing rollback steps before deploy turns a potential outage into a fast, calm fix.

How long should I monitor after a release?

Long enough to see real traffic hit the new version: watch error rates, logs, and key metrics for at least the first hour, and keep a looser eye for the rest of the day. A release is only done once it is confirmed healthy in production.

All templates

📦engineering

Software Release Checklist

Ship a release safely: freeze, test, stage, deploy, and monitor.

We'll add these tasks after you sign up. Free, no credit card.

How it works

A release goes wrong when steps are done from memory and one gets skipped under pressure. This template makes the release repeatable: freeze the branch, run the full test suite, update the changelog and version, stage and smoke-test the build, prepare rollback steps, deploy, then monitor. Apply it for every release so shipping is a calm checklist instead of a tense scramble.

What you get (7 tasks)

Freeze the release branchhigh~15m
Cut and freeze the release branch so no unreviewed changes slip into this version while it is being prepared.
#prep
Run the full test suitehigh~45m
Run all automated tests against the release branch and fix anything that fails before going further.
#testing
Update the changelog and versionmedium~30m
Write the changelog for this release and bump the version number so the release is clearly identified.
#prep
Stage and smoke-test the buildhigh~45m
Deploy the build to staging and run a smoke test of the critical paths to catch obvious breakage early.
#testing
Prepare rollback stepshigh~20m
Write down exactly how to roll back this release. Having the steps ready before deploy turns an incident into a quick recovery.
#prep
Deploy to productionhigh~30m
Push the release to production following the deploy process, and confirm the critical paths work live.
#deploy
Post-release: monitor errors and metricsmedium~45m
Watch error rates, logs, and key metrics for a while after the deploy. The release is not done until it is confirmed healthy.
#monitoring

Software Release Checklist

How it works

What you get (7 tasks)

When to use this

Frequently asked

Ready to use it?