Developer tools decision
Verceltics — Hosting & Domains
The project is open-source (MIT) and its GitHub is linked from the site, so a technical user can run or adapt the existing source rather than reimplementing the product; keeping a paid subscription is a convenience for users who prefer an App Store-managed binary and the full prebuilt 27 integrations.
Visit website↗Built by Apoorv, who ships 5 products in this index
$4.99/mo
$60/yr
Read off the official pricing page.
$20one-off6 h to build
$0/mo6 h/mo upkeep
On cash alone, building overtakes the subscription at 1 seat.
Open-source builds that already do this
Every project below is open source and already does this job today. Fork one, self-host it, or take the parts you need - the build prompt further down assumes an empty file, and this is the shortcut past that. Licences differ; check the one on each card before you ship. All Verceltics — Hosting & Domains alternatives, with the arithmetic →
What a replacement has to do
- Connect provider APIs, store device-only credentials, fetch provider-specific status/metrics, present per-provider dashboards and charts, and allow confirmed provider-bound write operations (DNS, deploy actions, renewals).
What it still won’t have
- Polished, production-grade iOS UX and iPad adaptive layouts
- The full set of 27 pre-built provider integrations
- App Store distribution and convenient install/trial handling
- Ongoing compatibility fixes for many provider API changes
What remains hard
- Product polish and ongoing maintenance
First-year cost
Keep paying
Paying is—cheaper in year one.
On cash alone, building overtakes the subscription at 1 seat.
Money you would actually spend
Time you would spend
—
What you would spend
What we assumed
The verdict above measures whether you could build it. This one is only about money.
Runnable build prompt
Build a minimal SwiftUI iOS app (iPhone + iPad) that manages hosting, registrar, and site-service provider integrations. Stack: Swift/SwiftUI, Combine/async-await, URLSession for HTTP, iOS Keychain for credentials, Codable + local SQLite or file cache for metadata, Charts for graphs. In scope: implement OAuth or API-key flows and secure device-only storage; adapters for at least 5 provider APIs (e.g., Vercel, Cloudflare, Netlify, Namecheap, Google Search Console) with read-only status and select write operations (DNS record edit, deploy trigger); per-provider dashboards with lists, tables, and charts; confirmation modal for destructive/writing operations; background refresh with rate-limit/backoff; unit tests for adapters and key UI flows; error handling and retry logic. Out of scope: App Store submission automation, analytics merging across providers, full set of 27 integrations, server-side credential proxy. Provide documented build/run steps and automated tests.
How we checked
How the score was reached
- Self-host verdict base92
- 2 cited sources+1
- Price verified on pricing page+3
- Evidence score96
The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time - so the same evidence always produces the same number.
How scoring works →Cited sources · 2
Every page the run actually retrieved.
- official productVerceltics — Hosting, Domains & Web Analytics for iPhone
- official docs27 Hosting, Domain & Analytics Integrations — Verceltics
Integrity checks
What held up, and what did not.
