VegaLoop is Live in Preview

Today, VegaLoop is live in preview.

If you build software for a living, you already noticed the date. It’s a Friday. The internet has spent two decades insisting you should never deploy on a Friday. We did it anyway. More on that in a minute.

The journey here

VegaLoop started the way a lot of useful things start: someone got frustrated enough to open a blank file and start typing.

The frustration was the same one a lot of people share. Nutrition lives in one app. Workouts live in another. Goals end up in a notes file or a spreadsheet. Each tool works fine on its own, but the moment you want to understand how your eating affects your training, or how a heavy week of activity should change what’s on your plate, you’re squinting at three screens trying to do the math in your head.

The earliest version of VegaLoop was barely software. It was a collection of scripts pulling data into one place so a single human could finally see what was actually going on. That phase didn’t last long, but it was long enough to prove the core idea. When nutrition, training, and recovery sit side by side, patterns show up that are invisible when they live in separate silos. We’ve written more about why we started building this if you want the longer version.

From there, the work was less glamorous: turning a personal tool into something other people could trust with their wellness data. That meant rethinking almost everything. A real platform has to handle the parent squeezing in three workouts a week, the runner deep in a marathon block, and the person who just wants to eat a little better without counting every gram. Different goals, different data, same underlying loop.

We made a few calls early that still shape the product. Nutrition and training share one system from the ground up, not two systems bolted together. The platform is designed for consistency over perfection, because real lives have bad weeks. And privacy is an architectural constraint, not a settings toggle you hope users find.

What “preview” actually means

Preview is exactly what it sounds like. It’s the platform working end to end, on real infrastructure, with real accounts and real data, available to a limited group of people who want to kick the tires and tell us what’s missing.

It is not feature-complete. It is not polished into every corner. There are rough edges we already know about and probably a few we don’t. That’s the whole point of opening it up now rather than waiting six more months for everything to feel perfect. The few people who used the prototype reshaped the platform in ways we couldn’t have predicted on our own. Preview is how we keep doing that, with more people, on something that actually resembles the product.

If you’re in the preview group, you should expect things to change. Features will improve. Some flows will get reworked.

About that Friday deploy

The rule about Fridays exists for a good reason. Ship something risky at 4 p.m. on a Friday, and you’ve handed your weekend to whoever is on call. There’s a reason engineers say it like a mantra.

But the rule assumes a few things. It assumes you ship rarely, so each deploy is a big event. It assumes nobody is around on the weekend to fix things. It assumes the cost of a small problem is high because rolling forward or rolling back is slow and painful.

None of that describes us. We ship constantly. The deploy pipeline that took us from a pull request to production today is the same one that runs dozens of times a week. The team is around. Rolling back is a few commands, not a few hours. The blast radius of any one change is small by design. We’ve written about how that pipeline holds together for the engineering audience, but the short version is that “don’t deploy on Friday” is advice for a world where deploying is dangerous. We spent a lot of effort making sure it isn’t.

There’s also a more honest reason. The product was ready. Holding a launch for a calendar superstition is its own kind of risk. Momentum matters. The team has been pointed at this moment for a long time, and pushing it to Monday for the sake of folklore would have felt like flinching.

So we shipped on a Friday. If something breaks, we’ll fix it. If something breaks badly, we’ll roll back and fix it on Monday. That’s how it should work.

What you can do today

If you’re in preview, you can sign in and start using the platform. Log a meal. Connect a fitness watch. Set a goal that actually means something to you. Then come back tomorrow and the next day and let the patterns start to surface. The product gets more useful the more it has to work with.

If you’re not in preview yet, you can request access from the home page, and we’ll bring people in as we expand the group. We’re being deliberate about pace because preview is a conversation, not a stampede. The more we can keep the feedback loop tight, the better the product gets before we open it up wider.

Either way, this is the part of building something where the work stops being a thing we’re describing and starts being a thing you can actually use. That’s worth showing up for, even on a Friday.

Welcome to the loop.