Verceltics is an independent, open-source operator workspace for the infrastructure and site services developers already use. Each provider keeps its own dashboard and capabilities; Verceltics supplies the native navigation, secure local credential storage, responsive caching, and iPhone/iPad interface around them. The main branch documents the current source build and can be ahead of the latest App Store release.
Version status: iOS 2.1 (43) is the current App Store release.
Android 1.0 (44) is in a Google Play closed beta; it is not publicly released yet.
Screenshots and feature descriptions document the current source build.
Android beta
Verceltics for Android has all 27 integrations and the same Pro plans as iOS.
To test it:
- Join the Verceltics Testers Google Group.
- Once the closed test is approved, opt in at
Google Play testing,
install Verceltics, and keep it installed for 14 days.
- Redeem
VERCELTICSBETA in Google Play for 30 days of Pro on the monthly plan.
After the free period it renews at the regular price unless you cancel. Valid until December 31, 2026.
Send feedback to [email protected] or use the app's About screen.
The iOS app is fully native SwiftUI. The Android app is a separate native Kotlin and Jetpack Compose app; it does not embed Flutter or share a cross-platform UI runtime. See Native mobile architecture for the current parity boundary.
Screenshots
The README highlights the iPhone experience. Verceltics also has a fully adaptive iPad interface; visit the website for the complete iPad gallery.
Supported providers
Verceltics 2.1 includes 27 separate integrations: 10 hosting platforms, 8 registrars, and 9 site services. Providers stay separated by the job they perform; Google Search Console and Google Analytics, for example, are independent connections and dashboards inside the Sites workspace. Available data and operations vary with each provider API, credential scope, account plan, and enabled service.
Hosting — 10
- Vercel
- Cloudflare
- Netlify
- Railway
- Render
- DigitalOcean
- Heroku
- Fly.io
- Firebase Hosting
- AWS Amplify
Registrars — 8
- Name.com
- Namecheap
- Porkbun
- Spaceship
- Dynadot
- NameSilo
- Gandi
- GoDaddy
Site services — 9
- Google Search Console
- Google Analytics
- PageSpeed & CrUX
- Bing Webmaster
- Microsoft Clarity
- Plausible
- Umami
- UptimeRobot
- Better Stack
What the app does
- Native workspaces — Hosting, Registrars, and Sites remain separate, with provider-aware dashboards and account menus.
- Cloudflare control — Accounts, zones, DNS CRUD, analytics, Pages, Workers, storage, security, cache, and guarded advanced API operations.
- Hosting dashboards — Projects, services, deployments, environments, domains, logs, jobs, bandwidth, channels, releases, and provider operation catalogs where supported.
- Registrar dashboards — Domains, expiry and renewal state, nameservers, DNS, contacts, transfers, privacy, certificates, and provider operation catalogs where supported.
- Separate site dashboards — Search Console, Google Analytics, PageSpeed, Bing, Clarity, Plausible, Umami, UptimeRobot, and Better Stack each open independently.
- Deep provider data — Search performance, indexing, sitemaps, URL inspection, GA4 reporting, Lighthouse and CrUX, uptime, response time, and availability.
- Responsive caching — Sites can reopen from protected, backup-excluded local snapshots; other recently viewed dashboards use in-memory cache. Data refreshes when the app becomes active, and pull to refresh remains available.
- iPad layout — Sidebar-adaptable navigation, adaptive grids, wider detail surfaces, and full-width charts on regular size class.
- Appearance — System, light, and dark modes.
- Guarded operations — Cross-host redirects are blocked; detected writes, purchases, and destructive requests require confirmation.
- Open source — The complete SwiftUI app, native Android app, and Next.js website are available in this repository.
Privacy architecture
Provider credentials and Google OAuth tokens are stored with device-only, when-unlocked iOS Keychain protection on iPhone and iPad, and encrypted with Android Keystore in app-private storage on Android. Provider-data requests go directly from the app to provider HTTPS APIs or an explicitly selected HTTPS host for supported self-hosted services.
iPhone / iPad
├─ device-only iOS Keychain
├─ protected, backup-excluded local snapshots
├─ HTTPS ───────────────────────────────> selected provider API
└─ credential-free public IPv4 lookup ─> api.ipify.org (registrar setup only)
No Verceltics credential proxy or provider-data server sits in between.
- No app tracking or advertising SDK
- No provider-data telemetry
- No third-party favicon service; favicon checks stay on the project site's own HTTPS origin
- Registrar setup can request the device network's public IPv4 from ipify without credentials or provider data. Namecheap stores the explicitly accepted address as required
ClientIp connection metadata and sends it with Namecheap API requests; Name.com only copies it to the system pasteboard after an explicit action and never saves or sends it as a Name.com credential.
- Google API data is used only for the connected user-facing feature and handled under Google's Limited Use requirements
- The website has no client-side analytics and is delivered through Cloudflare Workers Static Assets
Read the complete Privacy Policy and Security Policy.
Pricing
| Plan | Price | Trial |
|---|
| Monthly | $4.99/month | None |
| Yearly | $34.99/year | 7 days for eligible first-time subscribers |
| Lifetime | $59.99 once | Not applicable |
All paid options unlock the same Verceltics Pro entitlement. App Store pricing can vary by country, currency, and tax. The source is MIT-licensed and may be built or modified for personal use; personal builds require their own provider credentials and any OAuth configuration needed by the selected Google integrations.
Tech stack
iOS
- SwiftUI with sidebar-adaptable
TabView
- Swift Charts for native, interactive analytics
- Swift 5 language mode with main-actor default isolation and structured concurrency
- Observation (
@Observable) and async/await
- iOS Keychain for device-only credential storage
- RevenueCat + StoreKit for subscriptions, lifetime access, optional tips, and restoration
Android
- Kotlin with Jetpack Compose and Material 3 native interactions
- Android Keystore-backed credential protection and app-private, backup-excluded storage
- A native provider catalog covering all 27 integrations
- Native flows for all 27 integrations, multiple accounts per provider, and the RevenueCat paywall with Google Play Billing
Web
- Next.js App Router with static export
- React and TypeScript
- Tailwind CSS v4 plus a custom app-matched design system
- Cloudflare Workers Static Assets via Wrangler
Repository structure
verceltics/
├── android/ # Native Kotlin and Jetpack Compose Android app
├── ios/ # SwiftUI iPhone and iPad app
├── web/ # Next.js website, privacy, and terms
├── docs/screenshots/ios/ # Current iPhone screenshots used by this README
├── docs/screenshots/ipad/ # Current iPad screenshot source assets
├── scripts/ # Provider catalogs, test runners, and CI helper scripts
├── store/ # Store listings, product catalog, and release switches
└── tests/ # Catalog and request-integrity tests
Run the iOS app
-
Clone the repository.
git clone https://github.com/apoorvdarshan/verceltics.git
cd verceltics
-
Open ios/verceltics.xcodeproj in Xcode.
-
Select your Apple development team in Signing & Capabilities.
-
Choose an iPhone running iOS 18 or later, or an iPad running iPadOS 18 or later.
-
Build and run.
Production App Store entitlements are managed by Apple and RevenueCat. A source build still needs your own provider credentials and any OAuth configuration required by the Google integrations you intend to test.
Run the Android app
The Android project requires JDK 17 and Android SDK Platform 37.0.
cd android
./gradlew assembleDebug
Open the android directory in Android Studio to run the app on an Android emulator. See the parity matrix for what each provider workflow supports.
Android Google sign-in (Search Console, Google Analytics and Firebase Hosting) uses the same public OAuth client as iOS, with the browser PKCE flow and the client's reverse-ID redirect scheme. A fork can use its own client by adding it to ~/.gradle/gradle.properties:
VERCELTICS_GOOGLE_OAUTH_CLIENT_ID=123456-example.apps.googleusercontent.com
Android purchases use the same RevenueCat project, Verceltics Pro entitlement, and product IDs as iOS. Add the RevenueCat Google Play public SDK key to ~/.gradle/gradle.properties:
VERCELTICS_REVENUECAT_API_KEY=goog_example
Release builds for Google Play are signed with the upload key named in ~/.gradle/gradle.properties. The key and its password file stay outside the repository:
VERCELTICS_UPLOAD_KEYSTORE=/path/to/verceltics-upload.jks
VERCELTICS_UPLOAD_KEYSTORE_PASSWORD_FILE=/path/to/password.txt
Without them, release builds are unsigned. Release automation signs with the same upload key
from the ANDROID_KEYSTORE_* repository secrets; see store/README.md.
Builds without a RevenueCat key keep Pro locked and show "Plans unavailable" on the paywall. Debug builds may use a RevenueCat Test Store key (test_...), but release builds refuse one because the SDK crashes on it, and bundleRelease requires a goog_ key. In RevenueCat, mark the Google Play lifetime product as non-consumable and the four tips as consumable.
Run the website
The website uses https://verceltics.com/ as its canonical origin. Its Cloudflare
Worker redirects HTTP, www, and known HTML aliases before serving static pages.
The October 3 SEO review records Search Console
findings, implemented changes, and the indexing follow-up.
cd web
npm install
npm run dev
Open http://localhost:3000.
Create the production static export:
npm run build
Deploy the exported web/out directory through the configured Cloudflare Workers Static Assets project:
npm run deploy
Discord community bot
Vercie runs on the website's Cloudflare Worker. It handles /ask for app help,
/bug and /feature for public GitHub issues, and optional store release
announcements. See Discord setup for credentials,
server command registration, and deployment.
Join the Verceltics Discord community for help.
In the app's About screen, Report an issue and Request a feature offer
two routes:
Both routes create public GitHub issues. Redact credentials, private account
data, and screenshots before submitting. /bug and /feature share a five-minute
per-user cooldown. Report vulnerabilities privately using SECURITY.md.
Authentication model
| Category | Authentication |
|---|
| Vercel | Personal access token |
| Cloudflare | Scoped API token, or email + Global API Key |
| Other hosting providers | Provider token/key; Firebase Hosting uses Google OAuth |
| Registrars | Provider API key/token and any provider-required account metadata |
| Google Search Console / Analytics | Google OAuth with the documented read-only scopes |
| Other site services | Provider API key/token or user-selected HTTPS host where supported |
The app validates and scopes credential use to known provider hosts. Advanced operation catalogs expose provider-relative APIs; review every write request before confirmation.
Testing
Run the repository tests (provider catalogs, privacy manifest, CI helper scripts, the offline store
release scripts, and the store listings and screenshots):
./scripts/test.sh
Run the iOS unit (vercelticsTests) and UI (vercelticsUITests) tests on an iOS Simulator:
bash scripts/test-ios.sh
The script creates its own simulator and deletes it afterwards, so existing simulators are never
reset; it fails if either test bundle runs zero tests. UI tests launch the Debug app with
-uiTesting, a Simulator-only test mode compiled only into Debug builds: accounts stay in memory,
RevenueCat and App Store update checks are never contacted, and UserDefaults start empty. They
cover the developer welcome, first-run connection welcome, provider catalog, the Vercel token form,
the Hosting/Registrars/Sites/About tabs, the Search tab, the soft paywall on Pro details, and
persistence of the welcome, last workspace, and appearance across relaunches.
Run the native Android checks, then the instrumentation and Compose UI tests on an emulator:
cd android
./gradlew :app:testDebugUnitTest :app:lintDebug :app:assembleDebug :app:assembleRelease
./gradlew :app:connectedDebugAndroidTest
CI runs the same checks only for the files they cover: ios-tests.yml on the GitHub-hosted
xcode-27 runner, and ci.yml for the catalogs, website, Android build, and instrumentation tests
split across two API 36 emulators restored from a clean snapshot. Unit test results are never
restored from the Gradle build cache.
For purchase testing, use Apple sandbox or TestFlight together with RevenueCat customer history and entitlement tools. The checked-in StoreKit configuration mirrors the monthly, yearly, lifetime, and optional-tip products for local reference.
Disclaimer
Verceltics is not affiliated with, endorsed by, or sponsored by any supported hosting platform, registrar, or site-intelligence service. Provider names and marks belong to their respective owners.
Contributing
iOS (ios-v*) and Android (android-v*) tag and store automation is documented in
store/README.md. GitHub Actions builds, signs, and uploads both apps; Xcode
Cloud is no longer used for Verceltics and must not be re-created. Every store switch is off until
explicitly enabled, and a manual Run workflow only validates a signed build without uploading.
See CONTRIBUTING.md before opening a pull request. Our Code of Conduct applies to GitHub and the Verceltics Discord community. Report security issues privately using SECURITY.md.
License
MIT
Contact
Contributors
Star History
