← All posts

From JuzFlow to LairsFlow: Why We Renamed, and What Actually Changed

The story behind renaming JuzFlow to LairsFlow: what stayed the same, what moved to the new lairsflow.online home and Firebase project, and what it means for your data and your login.

If you have been using JuzFlow, the app just changed its name. It is now LairsFlow, living at lairsflow.online. Nothing you rely on went away. This post explains why the name changed, what moved under the hood, and what, if anything, you need to do.

The short version: same app, same features, same you. New name, new home, cleaner foundation.

Why rename at all

A name has one job, which is to be the thing people say when they mean your product. JuzFlow ran into two practical walls. The domain we wanted was not available, and the name bumped into existing brands closely enough to be a problem down the road. Neither of those gets better with time, so we changed the name while the product was still young.

LairsFlow was the answer, and it had a bonus going for it: it lines up with the parent identity, Lairs.bug. That makes the product and the people behind it read as one thing instead of two unrelated names. It is the name we want on the door for good. From here on, the product is LairsFlow, full stop. The one place the old naming tradition lives on is internal: our release codenames still come from Sanskrit, which is why the version you are using is called Vivran. Those are chapter titles, not the name of the book.

So this is not a pivot and it is not a fresh start. It is the same product finally wearing its real name.

What did not change

This is the important part, so it comes first.

If all you care about is that your habits still work, you can stop reading here. They do.

What moved under the hood

Two things changed below the surface, and both are worth knowing about.

A new home. The site now lives at lairsflow.online. Old links and old bookmarks should be updated when you get the chance, but the app itself is the same code serving the same screens.

A new backend project. LairsFlow now runs on its own dedicated Firebase project rather than the one it inherited from the JuzFlow days. In plain terms, that is the piece of plumbing that handles sign-in and cloud backups. Moving to a clean, correctly named project means the login and backup systems now match the product they belong to, with no leftover naming from the old world.

The web configuration for that project ships in the app, which is normal and expected. Those keys are meant to be public, and access to your data is still gated by authentication, not by hiding a config value.

What this means for your data

Because the backend project changed, here is the honest, practical guidance.

Your local data is safe. LairsFlow keeps your working data in your browser, so switching the site name and address does not touch what is already on your device.

For anything you had synced or backed up to the cloud under the old project, the cleanest path is the one the app already gives you: use Export or Backup to pull a copy of your data, then Restore it into LairsFlow. This is the same round trip you would use to move between devices, and it guarantees your history lands intact in the new home. If you have never touched those buttons, they live in the account menu on every screen.

If you only ever used LairsFlow locally, there is nothing to do at all.

What comes next

With the rename settled, the next phase of work has a name of its own: Chintan. It is less about new screens and more about sharpening what already exists, security, performance, and the small rough edges in the interface. The rename clears the desk for that work, since we are no longer building on a foundation with the wrong name stamped on it.

That is the whole story. New name, new address, cleaner backend, and every feature exactly where you left it. Welcome to LairsFlow.

Every question is a data point. Make it count.

Free to start. Bring your own Gemini key when you are ready for the Advisor.

Start free