It's been a while since our last update — longer than we'd have liked. We wanted to explain why, and more importantly, show you what we've been building.
The truth is simple: this release took longer than planned because we didn't want to ship it half-baked. Uptime touches something people rely on to know when things break — that's not a module we were willing to rush. We'd rather be late and solid than on time and shaky. Thanks for bearing with us — here's what the wait got you.
The biggest piece of this update is a brand new service: Uptime. It's made up of two components — Monitors and Status Pages — and together they cover everything from "is my server still alive" to "how do I tell my users about it."
Monitors continuously check your infrastructure using a range of methods:
Ping
SMTP / POP3 / IMAP
DNS
TCP / UDP ping
URL checking, hosted directly on Flowtag
![\"\"](\"https://images.ctfassets.net/394xwns91s5x/1HJz22hQymieR9OGtQ7892/bd10b743a55190237af9b588e9afd669/Zrzut_ekranu_2026-07-30_214427.png\")
When a monitor detects an outage, Flowtag automatically creates an incident — a shared space where you and your team can discuss what's happening, track the timeline, and coordinate a response, all in one place.
Status Pages let you share that information with the people who actually depend on your app — your end users. You can:
Automate reports by connecting a status page directly to your monitors
Or write and publish updates manually, on your own terms
Status pages aren't just for incidents, either — you can also use them to announce planned maintenance windows, so users know downtime is coming before it happens.
And because we know status pages are as much about branding as they are about function, they now come in four themes:
Vanilla
Lavender
Lily
Orchid
![\"\"](\"https://images.ctfassets.net/394xwns91s5x/1T2vhjHQXJfDO4913bIjqY/f68f82e3c1f4c1c41b7c3c24a9ab5fda/statuspage-vanilla.png\")
![\"\"](\"https://images.ctfassets.net/394xwns91s5x/3PrrjpUZ4jcOq3qV2pevSk/4238bc53ec5c500660ac71a44ac4ab65/statuspage-lavender.png\")
![\"\"](\"https://images.ctfassets.net/394xwns91s5x/2vyCFJGifrQ5jKT780U4OZ/941ef03a06d619f1aab4a4070e27f8c9/statuspage-lily.png\")
![\"\"](\"https://images.ctfassets.net/394xwns91s5x/3hlh2wtn6g80EsAUW232a6/2a2de17046abd29aeb0d5d78e1ef3da5/statuspage-orchid.png\")
The dashboard got a visual overhaul, and the headline addition is a brand new homepage — a proper landing spot when you log in, instead of dropping straight into a single module.
![\"\"](\"https://images.ctfassets.net/394xwns91s5x/53fBoWoV1tB1JEvHwBbSuC/6bd78061d0d3eebe2ff761d573b75494/Zrzut_ekranu_2026-07-30_220217.png\")
We rebuilt the search engine under the hood, so finding what you need across your projects is noticeably faster.
Notifications also got attention this round:
A refreshed look across the board
Push notifications
, connectable right from your browser
Do Not Disturb mode
— flip it on when you're heading out on vacation and want to actually disconnect, without worrying about being paged
Even this blog got a refresh — you're looking at it right now.
We also added a dedicated contact page, so reaching us no longer means digging for an email address.
That's the update. Uptime has been the biggest single addition to Flowtag since launch, and we're glad to finally have it in your hands. As always, we'd love to hear what you think — reach out and let us know.
", "url": "https://flowtag.dev/blog/uptime-a-refreshed-dashboard-and-a-lot-more", "title": "Uptime, a Refreshed Dashboard, and a Lot More", "date_modified": "2026-07-30T20:03:23.468Z", "author": { "name": "QwertyCodeQC (Developer)", "avatar": "//images.ctfassets.net/394xwns91s5x/LPsJrc5Ab1lwg0Sf86wv0/b054a588017bff97c43a819cca5a0e93/167351530" }, "tags": [ "Product Updates" ] }, { "id": "https://flowtag.dev/blog/variables-developer-preview-ui-refresh", "content_html": "We're shipping two things today: Flowtag Variables is now available in developer preview, and we've refreshed the marketing site with a new hero and dedicated product pages.
Variables are small configuration files your application can fetch in ~100ms, globally — no cold starts, no polling, no stale state baked into a deploy.
There are two types:
Toggle — a boolean. On or off. Simple, but that's the point. Use it to gate a feature, enable a maintenance mode, or kill a rollout without touching your codebase.
JSON — a full configuration object for your application, with a built-in schema validator. You define the shape, Flowtag enforces it. No more shipping a config change and discovering at runtime that a key was missing or mistyped.
Together, they give you a control layer that's independent of your deployment pipeline. Change a variable in the dashboard, and your app picks it up — everywhere — in milliseconds.
Common use cases:
Feature flags per environment
Remote kill switches
A/B test configuration
Rolling out changes gradually without a redeploy
Variables is shipping today as a developer preview. That means the API isn't finalized — new features may be added, and existing ones may change. We want to get real usage in before locking things down.
We've refreshed the hero on flowtag.dev again — cleaner, tighter, more focused on what Flowtag actually is.
We've also added dedicated product pages so each module has a proper home:
There are also a handful of smaller tweaks across the dashboard — nothing dramatic, just things that were bothering us.
Variables is live. Try it, break it, tell us what's missing.
", "url": "https://flowtag.dev/blog/variables-developer-preview-ui-refresh", "title": "Variables Developer Preview + UI Refresh", "date_modified": "2026-05-16T15:07:47.742Z", "author": { "name": "QwertyCodeQC (Developer)", "avatar": "//images.ctfassets.net/394xwns91s5x/LPsJrc5Ab1lwg0Sf86wv0/b054a588017bff97c43a819cca5a0e93/167351530" }, "tags": [ "Product Updates" ] }, { "id": "https://flowtag.dev/blog/recent-service-disruption", "content_html": "On May 4th, several Flowtag services were unavailable for approximately 8 hours due to issues with our domain registrar. Our infrastructure was healthy the entire time — the problem was at the domain level, which made it harder to catch quickly.
We're not going into the specifics of what happened with the registrar, but we want to be upfront: it was our problem to manage, and we didn't handle it well enough to prevent the impact on you.
We're sorry for the downtime. We're putting monitoring in place so that domain-layer issues get caught and communicated much faster going forward.
— Flowtag team
", "url": "https://flowtag.dev/blog/recent-service-disruption", "title": "Recent service disruption", "date_modified": "2026-05-04T20:48:32.952Z", "author": { "name": "QwertyCodeQC (Developer)", "avatar": "//images.ctfassets.net/394xwns91s5x/LPsJrc5Ab1lwg0Sf86wv0/b054a588017bff97c43a819cca5a0e93/167351530" }, "tags": [ "Product Updates" ] }, { "id": "https://flowtag.dev/blog/flowtag-has-a-new-home-flowtag-dev", "content_html": "From day one, Flowtag ran under flowtag.qwerty.ovh — a placeholder that got the job done while we were still figuring out the right direction for the product. It was functional, but not exactly the kind of URL you'd confidently paste into a README.
That changes today. Flowtag now lives at flowtag.dev — a domain that actually matches what we're building. The app is live, the docs are there, and it's where everything new will happen going forward.
The frontend and dashboard move immediately to flowtag.dev. However, all existing API and infrastructure endpoints remain fully active under their current domains — they will stay up until we've fully migrated all services to the new domain. Nothing breaks for anyone already integrated.
Domain | Purpose | Status |
| App, dashboard, documentation | ✅ Active |
| Status page for Flowtag's services | ✅ Active |
| Flowtag's documentation | ✅ Active |
| Analytics beacon / ingestion | ✅ Active |
| Legacy documentation domain | ⏳ Migrating |
| Legacy app domain | ⏳ Migrating |
| Public API endpoints | 🔒 Active until full migration |
| Analytics beacon / ingestion | 🔒 Active until full migration |
| Status page for Flowtag's services | ❌ Inactive |
No action required on your end. If you have
flowtagapis.qwerty.ovhorflowtagbeacon.qwerty.ovhhardcoded anywhere — in your SDK config, environment variables, or tracking snippets — they will continue to work without interruption until the full migration is complete.
There's no deadline pressure right now. The old domains will remain fully operational for as long as it takes to move all services over. We'll announce the deprecation date well in advance — with enough time to update your integration at your own pace. When new API domains are ready, we'll publish updated endpoints alongside a clear migration guide.
If you're starting a new integration today, we recommend waiting for the new endpoint documentation before embedding any domain directly. Reach out if you're unsure what to use.
Moving to flowtag.dev is part of a broader effort to make Flowtag feel like the production-grade platform it's becoming — not a side project running under a dev subdomain. The domain is a small thing, but it matters for trust, for SEO, and for the kind of experience developers expect from tools they put in their stack.
More updates are coming soon. The new domain gives us a clean foundation to build on.
Questions or feedback? Write to us at hello@flowtag.dev. We'll update this post as the migration progresses.
", "url": "https://flowtag.dev/blog/flowtag-has-a-new-home-flowtag-dev", "title": "Flowtag has a new home — flowtag.dev", "summary": "We finally got a real domain. Say hello to flowtag.dev.", "date_modified": "2026-04-19T14:44:09.447Z", "author": { "name": "QwertyCodeQC (Developer)", "avatar": "//images.ctfassets.net/394xwns91s5x/LPsJrc5Ab1lwg0Sf86wv0/b054a588017bff97c43a819cca5a0e93/167351530" }, "tags": [ "Product Updates" ] }, { "id": "https://flowtag.dev/blog/ui-refresh-and-experimental-analytics", "content_html": "We've been quietly shipping. This update is a mix of visual polish and two new experimental analytics features that change how you explore your app's data. Here's what landed.
The dashboard has a new color palette — cooler, more blue-leaning tones throughout. It's a subtle shift, but it makes the interface feel more focused and less fatiguing during long sessions. Blues tend to recede visually, which means your data gets to be the loudest thing on the screen.
corner-shape: squircleWe're testing a new shape language across the UI using the CSS corner-shape: squircle property. Squircles — the shape used in iOS app icons and modern design systems — have smoother, more organic curves compared to standard border-radius rounding. It's a small detail, but the kind that makes an interface feel considered.
This is experimental for now. Browser support is still catching up, so you may see differences depending on your browser.
A handful of small UI inconsistencies got squashed — mostly alignment and spacing issues that were bothering us more than they should have.
Flowtag Analytics now includes Page Discovery — a way to explore your app's pages the way you'd browse a file system.
Instead of a flat list of URLs, pages are organized hierarchically by path. Drill into /dashboard, then into /dashboard/settings, then deeper. Each node shows traffic and engagement stats for that specific page.
Example: Say you're running a SaaS app and you notice overall engagement is dropping. With Page Discovery, you can drill into /app/onboarding and see that /app/onboarding/step-3 has a sharp drop-off in pageviews — users are bouncing at step 3. That's the kind of signal that was previously buried in a flat URL table.
It's especially useful when your app has deeply nested routes or dynamic paths with lots of segments.
Event Browser gives you a direct, unfiltered look at the events Flowtag is capturing from your app.
No charts, no aggregations — just a browsable stream of raw events with their full property payloads. Filter by event name, browse by session, inspect exactly what was sent. It's the fastest way to verify that your instrumentation is working, debug a specific user flow, or just get curious about what's actually happening.
Think of it as a one-step shortcut from "I wonder if that event fires correctly" to having your answer — without opening a separate tool or digging through logs.
Both features are experimental and actively developed. If you run into anything unexpected — or have thoughts on where this should go — reach out.
We have to share some less exciting news: Variables is being delayed to June 2026.
This one stings a little to write. We had a target in mind, and we're moving it. But we'd rather take the extra time and ship something we're genuinely proud of than rush a release that doesn't meet the bar we've set for ourselves. Edge config is infrastructure — it needs to be right.
We'll share more when we have a concrete timeline. Thanks for your patience.
We're building this in the open, one piece at a time. If you have feedback, we're listening.
", "url": "https://flowtag.dev/blog/ui-refresh-and-experimental-analytics", "title": "UI Refresh & Experimental Analytics", "date_modified": "2026-04-10T19:05:20.210Z", "author": { "name": "QwertyCodeQC (Developer)", "avatar": "//images.ctfassets.net/394xwns91s5x/LPsJrc5Ab1lwg0Sf86wv0/b054a588017bff97c43a819cca5a0e93/167351530" }, "tags": [ "Product Updates" ] }, { "id": "https://flowtag.dev/blog/flowtag-update-v2", "content_html": "A lot shipped recently. Here's the rundown.
The old dashboard was showing its age. We cleaned it up — better layout, less noise, the important stuff is easier to find. Nothing revolutionary, just a much more pleasant experience day to day.
We rewrote the entire analytics core. The main reason: event tracking. The old system gave you numbers, but not enough context around them. Now you can track specific events and actually understand what's happening in your app, not just that something happened.
It was a bigger undertaking than we expected, but it's the right foundation for what comes next.
Fresh coat of paint. If you haven't visited flowtag.qwerty.ovh recently, it looks quite different now.
We launched a blog. You're reading it.
This is the one we're most excited about.
Variables lets you configure your app in real time from the Flowtag dashboard — no redeploy, no code change. You define a variable, reference it in your app, and update it whenever you want. The change propagates instantly.
It's early, but we already use it ourselves for things like toggling features and adjusting settings across environments. More on this soon.
That's the drop. More coming.
— Flowtag Team
", "url": "https://flowtag.dev/blog/flowtag-update-v2", "title": "Flowtag Update v2", "summary": "New content added to flowtag platform!", "date_modified": "2026-03-22T12:41:14.388Z", "author": { "name": "QwertyCodeQC (Developer)", "avatar": "//images.ctfassets.net/394xwns91s5x/LPsJrc5Ab1lwg0Sf86wv0/b054a588017bff97c43a819cca5a0e93/167351530" }, "tags": [ "Product Updates" ] }, { "id": "https://flowtag.dev/blog/welcome-to-flowtag-blog", "content_html": "Hi,\nIf you see this text that means the blog is working correctly!\n
Here you'll see all the news and stories from Flowtag creators!
ol
list
ul
list
Amazing Quote!
Italic
Bold
Underline
![\"\"](\"https://images.ctfassets.net/394xwns91s5x/6C4rhjJejA0bIAJEiTppxc/022af2a637b7f6c48c06f778dec4d008/741-1920x1080.jpg\")
Table | Header |
|---|---|
Table | Cell |