Company
Why we're building Fwoop
Owning your servers should be the easy choice, not the brave one. Here's what we believe and what we're building.
The Fwoop team 2 min read
A VPS today is absurdly good value. For the price of a team lunch you get more CPU and memory than most products will ever need, in a data centre near your users. Bare metal is better still. And yet a lot of teams still treat running their own servers as a brave choice, something you do once you’ve hired a platform team.
We think that’s backwards, and we think the reason is tooling.
The gap
Running a product on your own servers takes a handful of things: deploying it, scheduling the jobs around it, backing up its data, watching its health and keeping its secrets. Each one has excellent open-source tools. Docker Compose for deploys. Cron for schedules. restic for backups. A dozen choices for monitoring.
What’s missing is the glue. Who deployed what, to which servers? Which jobs run where, and did last night’s run succeed? Is the backup restorable? Who gets the alert? In most teams, the answers live in shell history, a wiki page that was accurate once, and the head of the person who set it all up.
That’s the gap Fwoop fills: one control plane that ties those tools together across every server you run, so the answers have a single place to live.
What we believe
Your infrastructure should stay yours. Fwoop runs your workloads on machines you control and sends backups to buckets you own. We store configuration and metadata, not your data.
Boring tools are a feature. We’d rather build on Compose, cron syntax and restic than invent new formats. If you stop using Fwoop, your compose files still work and your backups are still restorable.
Safe should be the default. Outbound-only agents, encrypted secrets, verified backups and an audit log aren’t premium extras. They’re how it works from the first server.
Small teams deserve good ops. A two-person startup should be able to run production with the same confidence as a company with a platform team, without having to become one.
Where we are
Fwoop is in early access. We’re onboarding teams in small batches, listening a lot, and shipping every couple of weeks; the changelog has what’s new. If you run your own servers and any of this sounds familiar, we’d love to hear from you. Book a demo, try the live demo, or just say hello.