Built by the people who run it
CloudForge is made by CLC Technologies (Pty) Ltd, an IT company in Cape Town, South Africa. We built it to host our own customers' sites properly - and then opened it to everyone else.
CLC Technologies looks after networks, cameras and IT for businesses, schools and community security districts. Hosting customer websites used to mean a collection of servers, plugins and renewals. CloudForge replaced that with one platform: a site is a tenant, a domain is verified and certified, publishing is a version, and every extension is a switch.
The platform runs as two copies - a development instance where every change is tested against real sites, and production, which only ever receives a build a person has approved. What you read on this site is how it works today, not a roadmap.
How CloudForge grew
Dated from the platform's own release record.
The first tenant
The first database schema: tenants, domains, pages, settings. One site, one domain, one place to run it.
The first tenant
The first database schema: tenants, domains, pages, settings. One site, one domain, one place to run it.
Sign-in in front of anything
The identity-aware gateway goes live: Microsoft sign-in and membership rules in front of any application behind the hub.
Sign-in in front of anything
The identity-aware gateway goes live: Microsoft sign-in and membership rules in front of any application behind the hub.
Two instances, one lane
A development copy of the platform behind production, and a written promotion process from one to the other.
Two instances, one lane
A development copy of the platform behind production, and a written promotion process from one to the other.
Extensions, templates, analytics
Extensions become packages with their own releases; eight starter templates; website traffic analytics rebuilt around people versus bots; roles and capabilities per tenant.
Extensions, templates, analytics
Extensions become packages with their own releases; eight starter templates; website traffic analytics rebuilt around people versus bots; roles and capabilities per tenant.
Audited and hardened
A performance, security and segregation audit, then the strict content-security policy, host-locked sessions, separated networks and a release lane measured in minutes.
Audited and hardened
A performance, security and segregation audit, then the strict content-security policy, host-locked sessions, separated networks and a release lane measured in minutes.
How we work
Measured, not assumed
A claim on this site is something the platform does today. Figures come from the platform's own records.
Additive and reversible
Changes to a live platform are made so they can be undone. Releases keep the previous copy warm.
A person answers
Questions, quotes and problems go to the people who build CloudForge, in Cape Town.
Talk to us
A site to move, an application to put behind the hub, or a question about how it works.