Skip to main content
TEN is the SaaS control plane that governs your CyberOS organisation: plan tier, seat headcount, billing, data residency, and the full lifecycle from signup to offboarding. If you are an organisation admin or on the finance team, TEN is where you manage seats, review invoices, configure data retention overrides, and — if the day comes — trigger the offboarding process with confidence that your data is portable and your exit is clean.
TEN is a P2 slice / P4 full module. The billing infrastructure ships at P2 to support vertical-pack pricing; full self-serve signup and the complete tenant-admin UI land at P4. Until self-serve is live, CyberSkill operations provisions tenants for vertical-pack customers. Contact your account manager to provision your organisation.

Plan tiers

Choose the plan that fits your team’s size and AI usage needs. All plans include the core CyberOS modules; higher tiers unlock advanced modules and increase resource limits.
Vietnamese organisations can pay in VND through Vietnamese PSPs (VnPay, Momo, ZaloPay). Contact your account manager for VND pricing details.

Module availability by plan

Some advanced modules are locked at the Free tier and unlock on upgrade:

Billing methods

CyberOS supports both international and Vietnamese domestic payment methods. PCI scope never touches CyberOS — card data is handled entirely by Stripe or the relevant Vietnamese PSP.
Pay by credit or debit card in USD, EUR, or SGD. Stripe generates your monthly invoice automatically. You can access all invoices in Settings → Billing → Invoices.Supported currencies: USD · EUR · SGDStripe handles all PCI compliance. CyberOS never stores or processes card numbers.

Usage metering

CyberOS meters usage across four axes. You can view real-time and historical usage in Settings → Billing → Usage.

Seats

The number of active Members in your tenant. Seat count is checked against your plan limit when you invite a new member.

AI tokens

Total tokens consumed across all modules in the current billing cycle. Checked against your monthly quota by the AI Gateway before every request.

API calls

Total API calls made to CyberOS services in the current billing cycle. Informational at current plan tiers.

Storage

Total storage used across BRAIN (memory), KB corpora, and file attachments. Checked against your plan’s storage cap.

Viewing usage in the billing dashboard

Navigate to Settings → Billing → Usage and select a billing period to see:
  • A breakdown of each metering axis against your plan limit
  • A daily time-series chart for AI token consumption
  • A per-module breakdown of API calls
  • A storage breakdown by data type (memory, KB, attachments)
You can also export a CSV of your monthly usage via Settings → Billing → Usage → Export CSV.

Data residency

When your tenant is provisioned, you choose a data residency region. This setting determines where your data is stored and which AI model endpoints are used for compliance.
Data residency cannot be changed after tenant creation. Choose carefully at signup.
Residency is enforced at every layer — Postgres shard, object storage region, AI Gateway provider selection, and OBS retention region. Your data never leaves your chosen region, even during a provider failover.

Tenant admin actions

As a tenant admin, you manage your organisation from Settings → Tenancy.

Seat management

1

Invite a member

Go to Settings → Tenancy → Seats → Invite Member. Enter the email address and select a role. The invitee receives a magic-link email. The seat is added to your active seat count when they accept.
2

Remove a seat

Find the member in Settings → Tenancy → Seats, click their row, and select Revoke Seat. Their login is disabled immediately. If they were assigned active tasks, reassign those before revoking.
3

Monitor seat utilisation

The seat count card in Settings → Billing → Usage shows your current seat utilisation against the plan limit.

Plan upgrade or downgrade

  • Upgrade — takes effect immediately. New modules unlock, higher quotas apply pro-rata, and a prorated invoice is generated.
  • Downgrade — takes effect at the end of the current billing period. If your usage exceeds the new tier’s limits, a 30-day grace period applies before enforcement. You will see a clear overage warning before confirming the downgrade.

Audit log

Your tenant’s full audit log is available in Settings → Tenancy → Audit Log. Every admin action — seat changes, plan changes, retention overrides, offboarding initiation — is recorded with the actor, timestamp, and a cryptographic chain link.

Data retention overrides

To configure retention overrides, go to Settings → Tenancy → Data Retention. You can increase retention beyond the platform default (for example, to meet a regulator’s minimum). Reducing retention below the default requires DPO sign-off.

Offboarding and data export

CyberOS provides a 90-day grace period on any cancellation — whether voluntary or due to non-payment — before any data is irreversibly deleted.
Offboarding is a two-confirmation process. You must type your tenant slug twice to confirm. Once the 90-day window expires, deletion is cryptographically attested and irreversible.

The 90-day offboarding timeline

GDPR Art. 20 data portability — signed export bundle

At any point during your tenancy (and throughout the offboarding grace period), you can generate a signed export bundle containing all your tenant data:
1

Request the export

Go to Settings → Tenancy → Data Export and click Generate Export Bundle. For DSAR requests, use Settings → Tenancy → DSAR Requests instead.
2

Download the bundle

The bundle is prepared within a few minutes and available for download for 24 hours. It includes:
  • All BRAIN memory files with audit chain segments
  • Per-module data exports (PROJ, CRM, KB, etc.) as SQL dumps
  • All file attachments
  • Full billing history and tenant configuration
  • A chain-of-custody manifest signed with Ed25519
3

Verify the bundle

The manifest includes SHA-256 hashes and an Ed25519 signature you can verify independently, proving the bundle is unmodified since export.

DSAR APIs

For data subject access requests under PDPL Art. 14 or GDPR Art. 15, use the DSAR endpoints in Settings → Tenancy → DSAR Requests. The bundle is automatically scoped to the data subject’s records across all modules.