Endless CC
Licenses
— Active
— Suspended
— Expired
Endless CC
Clients
Client registry and directory.
Endless CC
Server Health
Endpoint status, quota usage, and fingerprint alerts.
Checking…
—
Requests Today
—
of 20,000 daily limit
Quota Used
—%
warn at 80%
Active Sessions
—
heartbeats last 4h
Last Ping
—
response time
Daily Quota
Google Apps Script — resets midnight PH time
Fingerprint Alerts
New machine registrations pending review
No pending alerts
Grace Period Tracker
Clients currently in offline grace window
All clients online
Bookmarks
No bookmarks yet
Maintenance Log
No entries yet
Endless CC
Activity
Full audit trail of all Command Center actions.
Log
— entries
Endless CC
Generate Key
Create a new license key for a paying client.
New License
Basic = 1 seat. Enterprise = 3 seats. Adjust if custom deal.
Leave blank for one-time perpetual license.
Endless CC
Onboarding
Track the 7-step setup for each client.
Select a client
Choose a client above to view their onboarding checklist.
Endless CC
Settings
Global configuration for this Command Center instance.
Branding
Your CC identity and display name.
CC Name
Shown in the wordmark. Default: Endless
Owner Gmail
Your personal Gmail for reference.
Authentication
Passphrase and session settings.
Lock Command Center
End your session and return to the auth screen. Your data stays safe.
Change Passphrase
You will be locked out until you enter the new one.
Session Duration
How long before re-authentication is required.
Session expires
—
Server & Endpoint
Apps Script web app URL and quota settings.
Endpoint URL
Your deployed Apps Script web app URL.
Heartbeat Cache
Hours between heartbeat pings per client.
Grace Period
Offline days before soft warning is shown.
Pricing
Reference pricing per tier. Used in key generation display only.
Basic — One-time
Enterprise — One-time
Data
Backup, restore, and export your CC data.
Export Backup
Save encrypted .tfbak file to your device.
Restore Backup
Load a .tfbak file. Overwrites current data.
Export All Logs (CSV)
Download activity log as CSV.
Uplink — Cloud Sync
Push your CC data to the cloud. Pull it on any device.
Last push wins. Data is encrypted before upload — the server cannot read it.
This Device
Label shown in push metadata. e.g. "The Forge" or "The Field".
Push to Cloud
Upload encrypted snapshot to your endpoint.
Last pushed: Never
Pull from Cloud
Download and restore snapshot from cloud. Overwrites local data.
Last pulled: Never
Danger Zone
These actions are irreversible. Proceed only if you know exactly what you are doing.