AlfredoSELF-HOSTED

Ship your next SaaS in minutes.
Watch them all from one HQ.

Alfredo is the home for your projects. Your next one is live in minutes, with auth, email, database and analytics already wired. And every project you add is watched from one place.

landing-page
shipnote
cronpilot
snapkit

COUNTLESS TABS ONE HQ

Every new project makes you set up the same boilerplate again.

You have an idea. The waitlist needs email, so you set that up. Sign-ups need auth, and auth needs a database. Analytics, because you want to know if anyone shows up. Payments, because eventually you want to get paid. You have built all of this before, and you will build it again. Or you rent it: five managed services, five bills, none of it yours.

  • AUTHAGAIN
  • EMAILAGAIN
  • DATABASEAGAIN
  • ANALYTICSAGAIN
  • PAYMENTSAGAIN
SETUPS DUE5

Alfredo wires all of it once, on your own server. Your next project is live in minutes.

Inside the headquarters.

The views you get on day one, across every project you run.

ALFREDO OS 0.1HQ / HEALTHSIMULATED DATA
HEALTH · UPTIME KUMA + SENTRY1 NEEDS ACTION
ALL PROJECTS12/12 up
NEW ISSUES1 today
LAST INCIDENT6d ago shiplog
★ BEST STREAK41 DAYS ALL UP
UPTIME · UPTIME KUMACHECKED EVERY 30S
invoicer
shiplog
pantry-api
ERRORS · SENTRYACROSS 4 PROJECTS
NEWTypeError: cart is undefinedshiplog12 EVENTS · FIRST 3M AGO
OK429 RateLimitExceededpantry-apiRESOLVED 2D AGO
shiplog · TypeError in checkout.ts · needs actionSIMULATED FEED

Uptime and errors from every project in one view. Know something broke before the first user does.

YOUR SERVERS · ONE HQ · N PROJECTS

Every project you ship adds five more dashboards to check.

Traffic is in one tab, email delivery in another, payments in a third. That is one project. Ship a second and it all doubles. The setup eventually ends. The checking never does.

The fix is the HQ you just saw. Alfredo wired your stack, so Alfredo watches it.

BUT CAN'T WHAT I ALREADY USE DO THIS?

You probably already use something that does a piece of this.

Fair question. Most of these are tools we like and use ourselves. Here is the honest version: what you keep, what Alfredo adds, and when you should stay exactly where you are.

COMPARE AGAINST
Alfredo versus Coolify across seven capabilities: whether each is automatic, manual, or not possible.
PRODUCTRuns on your serversDeploys your projectsWires each project at birthOne dashboard across projectsSees your business, not just CPUWorks without assemblyFlat cost for many projects
AlfredoYour serversBuilt inThe coreAll projectsIncludedZero setupFlat, your box
CoolifyFree OSSMulti-serverYou connect itPer projectInfra onlyOps side is DIYFree self-host
DokployApache-2.0Compose nativeDo it yourselfPer resourceInfra onlyOps side is DIYFree self-host
GrafanaAGPL OSSNever deploysNot its jobYou build itDIY data sourcesConstruction kitFree OSS
DatadogSaaS onlyNever deploysPer-account setupStrongest todayOpt-in integrationsAgent + setupPer host, stacks
VercelNot self-hostGreat DXAdd-ons per projectOwn metrics onlyDeploy just worksScales with use
CloudflareTheir edgeWorkers / PagesPer-project bindingsOwn analytics onlyDeploy just worksGenerous free tier
SupabaseDocker, with gapsBackend onlyAuth, DB, storageOne backendManaged or Docker$0–599/mo
automatic manual not possibleVERIFIED JULY 2026

NOT FOR YOU IFSkip Alfredo if you enjoy wiring each project yourself, if you want zero servers and never think about ops, if you already run a happy Grafana or Datadog setup, or if you need deep APM, tracing, or a managed Postgres backend today. And Alfredo is an early, unproven prototype. Every tool above is the mature, proven thing.

FROM THE FOUNDER

I've shipped a lot of side projects. Every one made me set up the same boilerplate before the fun part could start, and every one left me another set of dashboards to check. Alfredo is me refusing to do that ever again. It runs on my server and watches my projects, and I want it to do the same for yours.

— Alper (@alperortac)

Every project runs on your servers and reports to one HQ.

Every project you'll ever ship already has a home.

Questions.

That's a journey you steer. Alfredo starts with Umami for analytics, Postmark for email, Convex for the database, Better-Auth for auth, Creem for payments, Sentry for errors, GitHub and Uptime Kuma. The lineup grows from what you ask for.

When you deploy a project, Alfredo creates the keys and config each integration needs and wires them in automatically. You never copy a secret into a .env file again.

On your own server. Any VPS you can SSH into works. Alfredo doesn't host your projects; you have full control.

Yes. Self-hosting only counts if you can read what you're hosting.

Your projects won't notice. Everything runs on your server, and the code stays open source.

You get exactly one email: the one that says Alfredo is live. Be one of the first inside.

WAITLIST · OPEN

Be there when Alfredo goes live.