Appearance
Customer Portal
The customer portal is an Anchor-operated service, separate from the customer-controlled proxy, policy engine, and dashboard. It processes account, licensing, billing, deployment, and release-delivery data as described in the public privacy notice.
After registering, your account is accessible at portal.bitdrip.app. Authentication is magic-link only — enter your email and use the delivered link.
What's in the Portal
License
View your current tier, expiry date, user limits, and deployment limits. Re-download your license.jwt at any time from this page — useful if you've lost the original welcome email or your license file was deleted.
Downloads
Download the current installer bundle and any prior versions. Links are tied to your account and do not expire.
Deployments
Each server running BitDrip registers itself with the portal on startup and on every phone-home check. The Deployments card shows:
| Column | What it means |
|---|---|
| Fingerprint | Unique identifier for that server instance |
| Hostname | Reported by the server (if detectable) |
| Version | BitDrip version string reported by the phone-home |
| Health | Current health status reported by the phone-home |
| Last seen | Most recent phone-home timestamp |
Health status values:
- healthy — all services (database and cache) are operating normally
- degraded — Redis is unavailable but the database is up; the service is running with reduced caching performance
- unhealthy — the database is unreachable; the service cannot serve traffic
A deployment showing unhealthy means the policy engine's database connection is down. A deployment showing degraded means Redis is unavailable — the service is still running but policy rule caching is disabled, which may increase evaluation latency.
You can revoke a deployment from this page. Revoking immediately prevents that server from validating new requests — useful when decommissioning a server or after a suspected compromise.
Your license has a maximum deployment count that varies by tier:
| Tier | Max deployments |
|---|---|
| Community | 1 |
| Team | 1 |
| Starter | 1 |
| Professional | 3 |
| Enterprise | High-volume deployment allowance by engagement |
Subscription & Billing
Manage your plan, view billing history, and access the Stripe billing portal for invoice downloads, payment method changes, and cancellation.
License Expiry
BitDrip sends automated warning emails 30 days and 7 days before your license expires, to the email address on your account. The portal also shows your expiry date prominently when it's within 30 days.
When a license expires:
- The Policy Engine continues running but enters a grace period
- New connections are blocked after the grace period ends
- Renewing via the portal restores full operation immediately
Phone-Home Behaviour
BitDrip checks in with portal.bitdrip.app at startup and periodically while running. The automated request contains these categories:
- authentication and license data used to validate the deployment
- The current deployment fingerprint
- The reported server hostname, when available
- The running version string
- The current health status (
healthy,degraded, orunhealthy)
Conversation content, prompts, policy configurations, and workstation end-user identity are not part of this documented portal check-in. The portal uses the listed data to validate licensing, track deployments against limits, and surface version and health information in the Deployments card. This automated check-in description does not describe separate support communications initiated by a customer; share only the diagnostic information requested and remove secrets and unnecessary content.
If the portal is unreachable, BitDrip operates normally under a 7-day grace period before enforcement is affected.
