Built for Day 2
Health, maintenance, lifecycle, and capacity are product problems, never afterthoughts.
Triton’s lineage runs from Joyent’s public cloud, through Samsung’s global cloud infrastructure, to the open-source platform we are building today.
We have spent years learning what it takes to operate cloud infrastructure after the demo is over: failures, capacity, networking, storage, lifecycle, multi-tenancy, and the systems operators depend on every day.
Triton Cloud carries those lessons forward rather than starting from a blank page.
Joyent built software to run its own public cloud. What began as SmartDataCenter evolved into Triton, the open-source cloud platform behind Joyent’s hosted cloud and its private-cloud deployments. Joyent introduced the Triton name in 2015 as the next generation of SmartDataCenter.
SmartOS · Zones · ZFS · SDN · APIs · Multi-tenancy
Source: Triton introduction, 2015
In 2016, Samsung acquired Joyent to gain its own cloud platform and cloud engineering capability, saying Joyent would help it scale infrastructure for mobile, IoT, and cloud-based software and services. Joyent’s CTO wrote that Samsung was expected to become the largest user of the technology while the platform stayed open source.
Samsung described the acquisition as the cornerstone of a connected cloud strategy and deployed Triton Private Regions around the world. One documented use: Samsung Cloud moved its object storage onto Triton Private Regions to control strategic data and its storage economics.
Global regions · Private Regions · Samsung Cloud · Strategic data
Sources: Samsung Newsroom, 2016 · CTO’s perspective, 2016 · Samsung Developer, 2017
In 2022, MNX Solutions acquired the Triton DataCenter technology suite and the commercial support business from Joyent, by then a Samsung company. Triton, Manta, and SmartOS kept their open-source licensing, and stewardship of the repositories moved with the platform.
Triton · Manta · SmartOS · Open source
Source: Transition announcement, 2022
Triton Cloud makes no attempt to freeze that history in place. It carries the operating experience, the open-source philosophy, and the cloud resource model forward while the control plane and infrastructure services are rebuilt for what comes next.
Open source · Cloud resource model · New control plane
A lineage is only useful when it improves what gets built next. Triton Cloud keeps what years of production operation taught us and rebuilds the parts the next decade of infrastructure demands. The past is an asset here, never a constraint.
Provisioning an instance is the easy part of running a cloud. The hard part comes later: failures, maintenance, capacity, isolation, upgrades, networking, storage, debugging, and keeping the system understandable after years of change.
Triton’s design is shaped by people and technology that have lived through those problems in production.
Health, maintenance, lifecycle, and capacity are product problems, never afterthoughts.
The infrastructure underneath the cloud stays visible and understandable to the people responsible for running it.
Projects, APIs, and self-service keep physical infrastructure out of the application team’s workflow.
Joyent open-sourced the Triton stack before the Samsung acquisition, and Samsung publicly committed to maintaining that open-source model. Triton, SmartOS, and Manta remained open source through the 2022 transition. Today the principle stays simple:
Run it with us.
Run it yourself.
Read the source.
The cloud platform we build is the platform we operate. Use Triton as a hosted cloud, or deploy Triton Private Cloud on infrastructure you control.
Same software. Same APIs. Different operator.
We have no ambition to out-feature every hyperscaler. We are building a focused cloud platform around a few principles:
The infrastructure landscape has changed. GPU density, open rack architectures, cloud economics, networking, and the expectations developers bring to infrastructure are different than they were when Triton began.
We are building Triton Cloud to apply what we have learned to the cloud we want to operate for the next decade.