Can Umami Cloud be vibe coded?
Open-source privacy analytics with a hosted cloud option
The software is open source, so the cloud subscription is mostly paying for managed hosting, upgrades, and not touching a server.
Jump to the build brief ↓Checked Jul 2026
What you pay today, before any DIY hosting
high editorial confidence
Buildability by layer
Screens, forms, and focused interactions
The repeatable job the product performs
Availability and legality of required data
Uptime, queues, support, and maintenance
Security, compliance, and user confidence
The achievable core
- Self-host Umami, install the tracking script, create websites/events, and maintain database backups.
- Ingest a known data source, calculate a focused metric set, and render a useful dashboard.
- A responsive interface with real empty, loading, success, and error states.
The parts a prompt cannot buy
- managed hosting
- upgrades
- reliability
- team/billing convenience
- Reliability at the vendor's scale is an operations problem, not a prompt.
Why people still pay
They pay because analytics is not worth waking up to fix.
Reliability at the vendor's scale is an operations problem, not a prompt.
The brief
Context, requirements, acceptance criteria, non-goals, and the full production standard — as Markdown, ready for any coding agent.
Build brief — a focused alternative to Umami Cloud
Context
**Umami Cloud** — Open-source privacy analytics with a hosted cloud option. It currently costs $9/mo.
The software is open source, so the cloud subscription is mostly paying for managed hosting, upgrades, and not touching a server.
This brief describes a focused, single-operator replacement for the part of Umami Cloud that is genuinely reproducible. It is deliberately narrower than the product it replaces, and it says so in writing. Build the useful core; do not pretend to have rebuilt the rest.
What you are building
Self-host Umami, install the tracking script, create websites/events, and maintain database backups.
Ingest a known data source, calculate a focused metric set, and render a useful dashboard.
A responsive interface with real empty, loading, success, and error states.
Requirements
Functional
VPS/Docker.
Database.
Domain/SSL.
Backups.
Update routine.
Non-functional
Accessibility: semantic markup, labelled controls, visible focus, and reduced-motion support.
Security: server-side secrets, validated input, and no credentials in the client bundle.
Reliability: retries with backoff on external calls, and a clear failure state when a provider is down.
Portability: the operator can export their data and leave without losing it.
Implementation brief
Build me a self-hosted analytics stack to replace Umami Cloud. Requirements:
Do not write analytics code. Umami is open source, deploy the real thing: a
docker-compose.yml with the official umami image + postgres:15, data in a named
volume. The subscription pays for hosting, so the build is a deployment.
All secrets in .env: postgres password and Umami APP_SECRET. Umami binds to
localhost; Caddy reverse-proxies stats.<mydomain> to it with automatic HTTPS.
backup.sh on a nightly cron: pg_dump to ~/backups/umami-YYYY-MM-DD.sql.gz, keep
14, with the restore command documented next to it.
update.sh: pull the new image, restart, and print the release-notes URL so I can
check for breaking changes before upgrading.
Add the tracking script tag to my sites and verify pageviews arrive; create one
custom event as proof the event pipeline works.
No third-party telemetry; visitor data stays in my postgres.
Out of scope: modifying Umami itself or building custom dashboards on top. And
accept the honest cost: uptime, upgrades, and 2am breakage are mine now.
README: DNS record for the stats subdomain, first-login default credentials, and
change the admin password immediately.
Delivery standard
Inspect the repository first, then write a short implementation plan before writing code.
Deliver the smallest complete end-to-end workflow first; every primary control must work against persisted data.
Use real validation and storage; never substitute fake dashboards, decorative controls, hard-coded success states, or mock integrations.
Include responsive layouts plus genuine empty, loading, success, validation, and failure states.
Keep secrets server-side in environment variables, provide .env.example, and never commit credentials or user data.
Add structured logs around every external call and return actionable errors without leaking sensitive details.
Write unit tests for the core logic and one automated test of the main user journey.
Finish with a README covering setup, architecture, data location, backups, tests, deployment, and known limitations.
Acceptance criteria
A clean install starts the app using only the README and .env.example.
The primary journey works from first visit through saved result, reload, edit, export, and deletion where applicable.
Invalid input, missing configuration, provider failure, and an empty database each have a usable state.
The interface works at 390px and 1440px, is keyboard navigable, and shows visible focus on every control.
Tests, type checking, linting, and a production build all pass with no ignored failures.
No part of the interface implies a live integration, security guarantee, or scale capability that was not actually built and verified.
Non-goals
Do not build these, and do not claim to have replaced them:
Managed hosting.
Upgrades.
Reliability.
Team/billing convenience.
Reliability at the vendor's scale is an operations problem, not a prompt.
What you still own after launch
Run migrations, backups, restores, and dependency updates.
Test the critical journey after every model, API, or hosting change.
Monitor failures and fix the edge cases a first prompt will miss.
Risk
**Operational risk.** The code is achievable; dependable data, integrations, and ongoing operations are the real cost.
Editorial confidence in this assessment: high. No independent one-shot implementation is linked yet.
Prior art
Working open-source software you can read, fork, or borrow from before starting:
[Umami](https://github.com/umami-software/umami) — The product's own open-source analytics platform
Generated by [Can It Be Vibe Coded?](https://www.canitbevibecoded.com) · Full report: https://www.canitbevibecoded.com/umami-cloud
You still own the product
- Run migrations, backups, restores, and dependency updates.
- Test the critical journey after every model, API, or hosting change.
- Monitor failures and fix the edge cases a first prompt will miss.
Open-source prior art
Before you start
Can Umami Cloud be vibe coded?
Yes, for personal use. The software is open source, so the cloud subscription is mostly paying for managed hosting, upgrades, and not touching a server.
What can an AI coding agent reproduce from Umami Cloud?
Self-host Umami, install the tracking script, create websites/events, and maintain database backups. Ingest a known data source, calculate a focused metric set, and render a useful dashboard. A responsive interface with real empty, loading, success, and error states.
What will a DIY Umami Cloud replacement still be missing?
managed hosting; upgrades; reliability; team/billing convenience; Reliability at the vendor's scale is an operations problem, not a prompt.
What do I still own after building a Umami Cloud alternative?
Run migrations, backups, restores, and dependency updates. Test the critical journey after every model, API, or hosting change. Monitor failures and fix the edge cases a first prompt will miss.