Berta Pulse
Berta Pulse
You've shipped a dozen things across Railway, Render, Vercel, Fly and Netlify — and you couldn't tell me which one 404'd last Tuesday. Berta Pulse watches all of them in one panel, tells you what's broken and what's wasting money, and pings you before your users do.
| Provider | Project | Status | Class | Waste |
|---|---|---|---|---|
| railway | side-blog | CRASHED | AUTO_FIXABLE | $18/mo |
| render | old-api | SLEEPING | NEEDS_CONFIRM | IDLE |
| vercel | launch-site | READY | HEALTHY | — |
| fly | demo-app | SUCCESS | HEALTHY | — |
You ship fast and spread thin. A launch here, a client demo there, an old API you forgot to turn off. Each lives on a different host with a different dashboard — so nothing is watched, nothing is documented, and you only find out something broke when it's embarrassing.
A project crashed three days ago. You found out because a user DM'd you, not because anything told you.
Railway, Render, Vercel, Fly, Netlify… five logins, five status vocabularies, zero overview.
That idle worker and forgotten preview env still bill you every month. Nobody's counting.
Restarting prod from memory at midnight — no dry-run, no undo, no record of what you did.
Most "ops dashboards" want your cloud credentials sitting on their servers. Berta Pulse doesn't. It runs locally — one command — and your keys stay in your own environment.
Start the dashboard with a single command — no account to create, nothing to deploy. It opens on localhost and talks to your providers straight from your own box.
Every provider token, GitHub PAT, GSC OAuth and AI key lives in your local env file. Berta Pulse reads them on your machine and never sends them anywhere.
We could get breached tomorrow and your AWS, Railway and Render keys would be untouched — they were never on our side to begin with.
Bringing AI fixes? Same rule — plug in your own OpenAI, Anthropic, Gemini or local Ollama key. We never proxy or store it. Every connector — each host, GitHub/GitLab, Search Console and the AI agent — has step-by-step setup documented right in the in-app Settings page, so you only enable what you use.
A proper weekly health check means logging into each provider, scanning each project, and eyeballing every service — one dashboard at a time. Berta Pulse does all of it in one scan.
every single week, across all 12 hosts
A realistic weekly status pass, host by host. Berta Pulse collapses all of it into a single scan you can run on a schedule — so the column on the right is effectively zero.
| Host | By hand, weekly | Manual time | With Pulse |
|---|---|---|---|
| Railway | login · list projects · per-service status | 1 scan | |
| Render | filter cron vs web · check each deploy | 1 scan | |
| Vercel | last deployment state per project | 1 scan | |
| Netlify | build status · which repo built it | 1 scan | |
| Fly | machine state per app | 1 scan | |
| Cloud Run | revision health per region | 1 scan | |
| Cloudflare · DO · Amplify | Pages / App Platform / release jobs | 1 scan | |
| Heroku · Koyeb · Coolify | dyno / app / container status | 1 scan | |
| 12 hosts | + context-switching between every tab | ≈ 2 hours | ~15 min total |
At even $75/hour for your time, 90 hours a year is ~$6,800 of your attention spent on logins and tab-switching — versus $108/year on Pulse annual. The subscription isn't the cost. The manual checking is. See it on a real fleet →
You've got a dozen things deployed and a nagging feeling one of them is down. Here's the difference.
Already shipping — and growing every week. Your subscription includes all of it.
Railway, Render, Vercel, Netlify, Fly, Heroku, Koyeb, Cloudflare Pages, DigitalOcean, Amplify, Cloud Run, Coolify.
Background scan every 15–60 min — Slack, email or webhook the moment a project goes auto-fixable or failed. This is the bit you'll never want to turn off.
Waste flags for idle services, stopped workers and forgotten preview envs are live today; full dollar-impact estimates are landing now. Included in Pro.
AUTO_FIXABLE vs NEEDS_CONFIRM; recovery recipes from real incidents; dry-run by default, only tier-0 auto-applies.
Discover domains, generate real sitemaps from your repo routes, push to GitHub/GitLab, submit to Google Search Console — no guessed URLs.
Pull every record — A, AAAA, CNAME, MX, NS, TXT, SOA, CAA — for all your sites in one pass, from your own machine. Snapshot before a migration, keep a backup, and diff after to prove you didn't drop MX, SPF or CAA. Export to JSON, CSV or a re-importable BIND zone file.
Scored GitHub portfolio linked back to your live hosts — open, jump to a service, or push a sitemap without copy-paste.
Ask it to diagnose and fix — an agent that reads the scan and proposes safe steps. Bring your own OpenAI, Anthropic (Claude), Google Gemini, or a local Ollama model. You pick the provider; the key stays on your machine and we never see it.
Append-only trail of every scan, preview, apply, push and alert — so you always know what changed and when.
Every provider token, GitHub PAT, GSC OAuth and AI key stays in your local env on your machine — never on our servers.
After push or GSC submit-all — per-site table with commit SHA, URL count, live status, and index analytics.
Sanitized previews — project names, domains and tokens blurred.
● GitHub connected · 144 repos · 12 linked to scan
| Score | Repository | Linked hosts | Actions |
|---|---|---|---|
| 82 | you/●●● | netlify · ●●● | Push |
| 54 | you/●●● | — | deploy · stale |
| 71 | you/●●● | railway · marketing | sitemap |
● GitHub connected ● GSC connected
| Site | Git repo | Live | Google index | GSC | |
|---|---|---|---|---|---|
| https://●●●.news/ | you/●●● | In git — redeploy | No impressions | In GSC | Push |
| https://●●●.app/ | you/●●● | In git — live | Indexed (12) | In GSC | Submit |
Keys loaded from .berta-pulse.env — this machine · Railway, Render, Vercel ✓
RENDER_API_KEY · rnd_●●●●●●●● — stored locally, never uploaded
GITHUB_TOKEN · GSC OAuth · AI key ✓ — all on-device
There isn't really another tool that watches every PaaS you use, fixes what's broken, and handles sitemaps — from your own machine. Uptime monitors ping URLs; APMs are built for big teams; each host only shows you itself. Here's the honest picture.
| Capability | Berta Pulse | Uptime monitors UptimeRobot · Better Stack |
Full APM Datadog · New Relic |
Each host's dashboard |
|---|---|---|---|---|
| All 12 PaaS hosts in one scan | ✓ | URL pings only | Setup-heavy | One host |
| Reads real deploy / service status | ✓ | Up / down only | Possible, complex | ✓ (one host) |
| One-click recovery playbooks | ✓ | — | — | Manual |
| Cost-waste tracking (AI-spend planned) | ✓ | — | Add-on | — |
| Sitemaps + Search Console (SEO) | ✓ | — | — | — |
| DNS record audit + export | ✓ | — | Partial | — |
| SSL / domain-expiry alerts | Planned | ✓ | Partial | — |
| Synthetic / functional uptime tests | Planned | ✓ | ✓ | — |
| BYOK · runs on your machine | ✓ | Hosted SaaS | Hosted SaaS | n/a |
| Starts at | $9–15/mo | $7–29/mo | $$$ / enterprise | Included |
| Status pages · phone-tree on-call · deep tracing | Not our focus | ✓ (Better Stack) | ✓ | — |
We're not an APM or a PagerDuty. Need deep tracing or a phone-tree escalation? Keep your monitor and add Berta Pulse as the multi-host ops + SEO layer none of them give you.
Pulse stays BYOK and local-first. Cost Doctor ships now in Pro; the rest are on the roadmap below. We'd rather show you what's real than pad a feature wall.
Idle and oversized infra flagged on your dashboard today; full dollar-impact estimates are landing now. Included in Pro.
On the roadmap — not built yet, not billable yet. They'll plug into the same dashboard and BYOK keys when they land.
Will track your BYOK AI spend (OpenAI, Anthropic, Gemini) — model-cost alongside Cost Doctor's infra-cost.
TLS-cert and domain-expiry monitoring per domain, with alerts before they lapse — a new column next to deploy status.
Scheduled HTTP and functional probes that check it's actually working — not just that it deployed.
Turns the watchdog into an interactive Slack app — fix buttons, slash commands and daily digests.
One-click migrate a project between providers (Netlify → Vercel and more), reusing the connector layer.
Earlier-stage candidates from the wider stack — landing as the catalog grows.
Start free today. Pro — the always-on watchdog and Cost Doctor — is landing soon. Want it for good? Grab the lifetime deal now and lock it in.
For getting hooked
Everything, always watching
Launching shortly — start free now and you'll be first to hear.
Pay once, founding member
167 of 200 lifetime seats left
No usage metering, no per-provider fees, no secrets stored. Cancel anytime — your data and keys were always on your machine.
The playbooks come from actual production incident sessions. The sitemap flow exists because guessed URLs failed in Search Console. We ship weekly and add hosts as builders ask for them.
Berta Pulse is built by Rondanini Publishing Ltd — a London company building "applied intellectual infrastructure" across publishing, financial education, and software (OrbaOS™, Cost Doctor, and more). Berta Pulse is the ops tool we built for ourselves: one local dashboard to keep a sprawling portfolio of side projects alive across a dozen hosts.
Same team behind berta.one. Questions or feedback? Get in touch.
Questions, feedback, or want a hand getting set up? Drop us a line — we read everything.