ByteDC
Cloud Platform · Phnom Penh, Cambodia

SaaS on ByteDC
A Sovereign SaaS Engine

Cambodian software. Cambodian data. In-country, by design.

The platform engine that lets any software vendor onboard their customers automatically — provisioning, secure login, billing, and in-country data residency — through a single connection.

↓ scroll  ·  → arrow keys
SaaS-on-ByteDC · concept & engine overview
The Concept

Four hard things, handled by one engine

Today, Cambodian software runs on foreign clouds — data leaves the country and regulated sectors can't fully adopt. ByteDC closes that gap: connect once, and every customer is onboarded for you.

Ready to use

The software is provisioned and configured automatically — no manual setup per customer.

Secure login

Customers sign in with their own company accounts — identity is federated, never stored by us.

Billing done

Subscription, metering and a single local invoice — taxes handled in-country.

In-country

Customer data stays inside Cambodia — residency and isolation by design.

Two onboardings — don’t conflate:  A · App-onboarding — the vendor lists their software on the platform (once).  ·  B · Customer-onboarding — each of their customers is set up automatically (this is what the engine does, every time).
A Two-Sided Program

Vendors gain customers · ByteDC runs the infrastructure

One program serving two markets at once — the software vendors, and the customers who buy from them.

Supply side

Software Vendors

Publish once, reach the Cambodian market.

  • Gain new customers through the platform
  • ByteDC hosts the infrastructure
  • Their software is deployed automatically for every customer
  • No per-customer manual operations
Demand side

Their Customers

Discover, subscribe, and start — instantly.

  • Software deployed & ready automatically
  • Secure login with their own accounts
  • Hosted in-country, billed locally
  • Upgrade to dedicated hosting anytime
Automated Deployment is the bridge between both sides — one publish by the vendor, and every customer is provisioned, onboarded, and live automatically.
Keeping software, data, and economic value in-country.
The Marketplace

List once — discovered, certified, delivered

Two distinct journeys: first the vendor gets their software onto the platform, then each customer is set up to use it.

A  ·  App-onboarding — the vendor puts their SaaS on the platform (once)
ISV / PartnerSubmit listing
partner portal
ByteDCCertify & approve
review listing
App-onboardingISV deploys the SaaS
listing published
↓  only approved & published apps appear in the marketplace
B  ·  Customer-onboarding — each customer is set up automatically
CustomerPick a SaaS
marketplace · featured / recommended
Customer-onboardingThe engine runs
provision · login · billing · in-country
ResultCustomer live
Two Hosting Models

Standard for scale · Sovereign for compliance

Multi-tenant

Standard

Customers share one running application, each in their own locked space.

  • For: SMEs & standard customers
  • Onboard: instant
  • Cost: lowest — near-zero marginal infrastructure
  • Data: in-country (logical isolation)
Single-tenant

Sovereign

Customer gets a fully dedicated, isolated stack — built on demand.

  • For: banks, government, regulated
  • Isolation: dedicated compute, network & account
  • Residency: data pinned inside Cambodia
  • Compliance-grade (NBC / gov-ready)
Move up anytime — a customer can start on Standard and be promoted to Sovereign later, keeping the same identity (no re-login, no broken links). The engine decides the path automatically: a regulated customer is always routed to a dedicated, in-country stack.
Engine Architecture

One connection, end to end concept

Vendors and their customers connect through a single platform. It composes everything needed to bring a customer live — then runs it on ByteDC's in-country cloud.

Software Vendors
publish once
Their Customers
subscribe
ByteDC SaaS Platform — one connection, one engine

Provision

set up the software

Identity

secure login

Billing

local invoice

Residency

in-country data

ByteDC Private Cloudin-country · Phnom Penh, Cambodia
How the Engine Decides

Routing — Standard vs Sovereign design

The path is a function of the app's tenancy model and the customer's required isolation tier. A required tier of L2 or higher forces the Sovereign (dedicated, in-country) path — even for an otherwise shared app.

onboardCustomer(vendor, customer, tier)
Read the app's tenancy model  +  the customer's required isolation tier
Routertier ≥ L2  OR  app is single-tenant ?
Standardmulti-tenant · shared
NO · L1
1
No infrastructurecall the vendor's create-tenant webhook
2
Identitycustomer org created · scopes the tenant
3
Billingshared / per-seat plan
4
Residencyalready in-country (logical) ✓
Sovereignsingle-tenant · dedicated
YES
1
Provision dedicated stackapply vendor recipe · automated deploy
2
Identitydedicated org · federates the customer's own login
3
Billingdedicated-instance plan
4
ResidencyL2 DB · L3 VPC · L4 account + data residency
Customer LIVESSO ready · billed locally · hosted in-country
Key — a shared app serving a regulated customer (bank / government) that requires L2+ residency is routed to a dedicated, in-country stack for that customer — while every other customer of the same app stays shared.
Sovereign Tier · Resource Footprint

What each tier consumes — in-country

Hosted on ByteDC's private cloud in Phnom Penh. As isolation rises, more of the stack becomes dedicated to a single customer — up to a fully isolated account.

LayerStandard · sharedSovereign L2Sovereign L3Sovereign L4
Public IPdedicatedCambodia IP pool residency
Compute (app)dedicateddedicated
Databasededicateddedicateddedicated
Network (VPC)dedicated VPCdedicated VPC
Account / quotadedicated account
Marginal infra / customer~zero+DB+full stack+isolated account

Cost and isolation climb together. Standard sells on volume at near-zero marginal infrastructure; the Sovereign tier — dedicated account + Cambodia-pinned IP — is the residency a hyperscaler can't offer, priced as premium.

Foundations

Engineered for trust, built to last

Proven

Already in production

Built on the same infrastructure that runs ByteDC's live platform today — not a greenfield experiment.

Automated

End-to-end

Every customer is provisioned, onboarded and deployed automatically — no manual steps per customer.

Secure

Federated identity

Customers use their own corporate logins; their credentials are never held by the platform.

Sovereign

In-country by design

Dedicated account, network and data for regulated customers — kept inside Cambodia.

Open

Vendor-neutral

Built on open, portable foundations — no lock-in to any single supplier.

Resilient

Durable & recoverable

Transactional orchestration with safe, automatic rollback if any step fails.

Design principle: reuse what already powers ByteDC's live platform; stay open and portable; add complexity only when a real need demands it.

Roadmap

From live platform to sovereign marketplace

Live now

Cloud Platform

Tier-III DC in Phnom Penh; self-service portal operating today.

Next

1-Click Catalog

ByteDC-curated apps, auto-deployed — proves the engine with our own supply.

Then

Open to Partners

Software vendors publish & sell — onboarding handled by the engine.

Then

Sovereign Tier

Dedicated, in-country hosting for banks & government.

The platform is live; the SaaS engine and marketplace are in active design. The path is incremental — each phase reuses the one before.

ByteDC · Cambodian software, Cambodian data, Cambodian-owned infrastructure.