Appwrite
See your Appwrite user growth, function health, storage footprint, and collection activity on your iPhone home screen without opening the console.
One credential, four views of your project
After a single setup with your Project ID and a read-only Server API Key, you choose which modules to place on your home screen. The Users module answers acquisition questions. The Functions module answers reliability questions. The Storage module answers capacity questions. The Custom Collection module answers data-flow questions for any collection in your project. Each module is independent and can appear as its own widget, so you can tune your home screen to the questions you actually ask every morning.
Glanceability as a forcing function
Appwrite's console is designed for deep investigation. PulseKit's widget is designed for a ten-second decision: do I need to investigate today? Seeing your 24-hour signup count, your function success rate, and your key collection's document inflow at once tells you whether to open your laptop or move on. When a number looks off, that is the signal to dig in. Until then, the widget confirms things are moving.
Tracking what matters, not everything
PulseKit pulls counts and rates that answer yes-or-no operational questions, not every stat Appwrite exposes. The Functions module reports your chosen function's success rate and 24-hour failure count, not duration percentiles that would require client-side aggregation across thousands of rows. The Custom Collection module tracks document growth in the collection you name, giving you a proxy for order flow, post activity, or whatever your schema represents, without requiring a separate query tool. Data is fetched on demand and chart history is retained for 30 days, so you can tell whether this week's numbers are normal or an anomaly.
How to connect Appwrite with Apple
Appwrite needs two values:
- Project ID - from cloud.appwrite.io → your project → Overview.
- Server API Key - from your project → Settings → API Keys → Create API Key. Pick the read scopes for users, functions, executions, databases, collections, documents, buckets, and files (or use "Read all" for simplicity). The key is shown only once.
We auto-detect which Appwrite Cloud region your project lives in.
Security
How we protect your credentials
Your Appwrite credentials (each field you typed) are joined on this device and sealed with AES-256-GCM before they ever leave your iPhone. Only your device holds the unwrap secret, stored in the iOS Keychain. The PulseKit backend wraps that already-encrypted payload again with its STORAGE_SECRET and writes the double-envelope blob to Postgres, so the server never sees any field in plaintext at rest. Each fetch request includes a one-time unwrap secret that decrypts the inner envelope only long enough to call Appwrite. Credentials are scoped to this device, can be revoked from PulseKit at any time, and are never written to logs.
What you can track
Pick the metrics you care about and pin them as widgets.
Users
Total users, new signups, and verified-user breakdown
- 64Total Users
- 53New Users (24h)
- 66New Users (7d)
- 26Verified Users
- 47Verified %
Functions
Per-function execution health: volume, failures, success rate
- 57Total Executions
- 94Failed Executions
- 23Success Rate
- 11Recent Executions (24h)
- 13Recent Failures (24h)
Storage
Per-bucket file count, footprint, and recent uploads
- 63Total Files
- 13Total Size
- 14New Files (24h)
- 73New Files (7d)
Custom Collection
Pick a database and collection to track document growth
- 16Total Documents
- 11New Documents (24h)
- 24New Documents (7d)
Numbers shown are illustrative — your widgets show your live data.
Who uses this
- Indie founders
The Users module puts your total user count and 24-hour signup delta on your home screen. Seeing new signups slow before your weekly review gives you time to check your onboarding flow or marketing spend, rather than discovering the drop days later inside the Appwrite console.
- Backend engineers
Cloud functions fail silently until users complain. The Functions module shows your chosen function's success rate, lifetime failure count, and 24-hour execution tally so you catch a regression the morning after a deploy, not days later buried in a support ticket.
- Full-stack developers
Storage costs accumulate gradually and bills arrive as surprises. The Storage module surfaces total file count and size in MB for any bucket, plus 24-hour and 7-day upload deltas, giving you a cost and activity signal that does not require navigating the Appwrite console.
- Product builders
Not every signal lives in user counts. The Custom Collection module lets you point at any database and collection in your project, such as orders, posts, or responses, and watch its document count and daily inflow on your home screen without writing a query or building a dashboard.
FAQs
How do I connect Appwrite to PulseKit?
Open PulseKit, tap Add Integration, and select Appwrite. You need two values: your Project ID from cloud.appwrite.io under your project's Overview, and a Server API Key created under Settings then API Keys. PulseKit auto-detects which Appwrite Cloud region hosts your project, so no manual region selection is required.
What Appwrite metrics can I see on my iPhone?
PulseKit surfaces 17 metrics across four modules. Users: total accounts, new signups over 24h and 7d, verified user count, and verified percentage. Functions: total executions, failed executions, success rate, and 24-hour activity and failures. Storage: file count, total size in MB, and new uploads over 24h and 7d. Custom Collection: total documents, and new documents over 24h and 7d.
Does PulseKit support self-hosted Appwrite?
Not in the current version. PulseKit connects to Appwrite Cloud only and auto-detects your project's region from the known cloud endpoints. Self-hosted support would require an additional endpoint field and is being considered for a future release.
What API scopes does PulseKit need for Appwrite?
PulseKit requires these read-only scopes: users.read, functions.read, execution.read, databases.read, collections.read, documents.read, buckets.read, and files.read. You can grant them individually or select Read All when creating the key in your project's API Keys settings. No write scopes are requested or used.
Can I track multiple Appwrite functions in PulseKit?
Yes. Add the Functions module more than once and pick a different function for each instance. Each widget or module tile tracks one function independently, so you can monitor your payment processor and your email sender side by side on the same home screen.
How does PulseKit find my Appwrite Cloud region?
PulseKit probes the known Appwrite Cloud regions in order when you first connect, using your Project ID to identify which one responds. The matching region is cached on your device and reused for every subsequent fetch. If a cached region returns an error, PulseKit re-probes automatically so you do not need to reconfigure anything after a credential rotation.
How fresh is the data shown in PulseKit widgets?
PulseKit uses on-demand fetching. Data updates when you open the app or manually refresh a widget rather than running continuously in the background. Chart history is retained for 30 days, so trend data is available even between refreshes.
Add Appwrite widgets to your iPhone
Install PulseKit, paste your credentials, pick a widget.