Solutions
One private cloud per agency. Records stay where you put them.
Ministers, permanent secretaries and national CIOs with a residency mandate, a thin budget and a decade of quotes that put the data abroad or the price out of reach.
Why now
The law now says where your records live.
The clocks are already running
The Philippines’ Executive Order 119 requires Secret data to be stored in Philippine territory and Confidential data to default to domestic storage on a three-year timeline. Kenya’s Cloud Policy 2025 entered into force on 2 May 2025 with localisation by data class. Korea is moving public cloud verification to a single NIS-led regime by the second half of 2027. [1]
SourceExecutive Order 119 (Philippines); Kenya Cloud Policy 2025; Korea N2SF transition note, April 2026. The full citation and link are in the footer notes.
What it means for you
Residency is no longer a preference in a tender. It is a clause with a date, and the auditor who checks it will ask for the placement record, not the brochure.
What waiting costs
Every month on a foreign region is a month of records you may have to move, re-contract or explain to an auditor. Moving later costs more than placing now.
Why Triple X
Triple X runs the same cloud on devices the state owns, inside its own buildings, with placement pinned and recorded. No new data centre, and no foreign operator reading your records.
In plain English
Your government has told you where its data must live. Triple X lets you meet that rule with equipment you own, at a cloud price, and prove it to the auditor with a placement record rather than a promise.
What you get
Four things, each a product you can open.
Devices the state owns
Racks and Triple X Cloud Nodes at sites you already control. Capacity grows by placing devices, not by building halls.
OpenOne private cloud per agency
Its own private network and placement pinned to named devices. Nothing reachable unless the agency publishes it.
OpenSealed for the records no one may read
Unreadable while in use, including to the operator, with a receipt for your auditor.
OpenFailover that respects the border
Work pinned to named devices fails over only between the devices you named.
Open
Which way in
Start where it fits. Move later without a new vendor.
Triple X Cloud nodes
No hardware of your own. Join the waitlist and start when your seat opens.
Your own devices
Triple X connects your racks or devices to a private cloud of your own.
Both
Sensitive work on your devices, the rest on ours, one private cloud.
Objections you will hear
What someone in the room will say.
We need a data centre, not devices.
You need capacity you own, inside your control, that survives one building losing power. Many nodes at sites you already control is that, without the capital or the four-year build.
A foreign company will run our cloud.
You own the devices and the data. The platform operator runs the scheduling and billing and sees that a workload exists and how big it is, not what is in it. The split is a table in the agreement, and it is on the Security page.
What about classified data?
Classified workloads run on devices pinned to named locations, with Sealed where no operator may read the data in use. The placement is recorded for your regulator.
Who certifies this?
The platform holds a SOC 2 Type II attestation with an unqualified opinion. CMMC Level 2 is pursued; FedRAMP is aligned, not authorized. Your own classification regime maps onto the four tiers.
What yes looks like
The list a buyer brings to the table.
- The state owns the hardware and the data; the operator cannot read either
- Every device pinned to a named location
- It survives a single site, a single switch, a single vendor going dark
- A ten-node pilot in one ministry before any national commitment
- A procurement path through a local company you already know
- A price per workload below the last foreign quote, with no exit fee
Get started
Start with one ministry and ten nodes.
A paid pilot with a pass mark you set.
- 01
Join the waitlist.
Tell us what you want to run and where. No credit card.
TakesTwo minutes
- 02
Run the pilot.
Ten nodes, 60 days, a pass mark you set in writing.
Takes60 days
- 03
Decide on day 60.
Extend, or leave at the transfer rate and nothing else.
WhoYou
We never ask for your root credentials, API keys or bank details by email.
The first 60 days
A pilot with a pass mark you set.
One ministry, ten nodes, a pass mark the CIO writes before the first device is plugged in.
Week 1
Your private cloud and ten devices at one site
Triple X connects ten devices at one ministry site to a private cloud with its own network. The first workload is a non-classified records system, placed on named devices.
Weeks 2 to 4
The ministry's own test
Run the real records workload with placement pinned. Pull the power on one device and time the recovery. The pass mark is the CIO's: residency held, recovery inside the tier commitment, cost per workload below the last foreign quote.
Day 30
Review with the audit office
Read the placement record, the operator access log and the first hourly invoice beside the foreign quote. The SOC 2 report is read under NDA.
Day 60
Decision
Extend to a second ministry, add Sealed for the records no one may read, or stop. Leaving costs the transfer rate and nothing else.
Questions
What buyers ask before they sign.
In the order they come up. Every answer ends with where to check it.
10 answers
All questionsWill the records stay inside buildings the ministry controls?
Yes, if you place them there. Devices you own at sites you control join your private cloud. Placement is pinned to named devices before anything is scheduled, and work pinned to named devices fails over only between the devices you named.
Proofthe pinned placement control on the Security page and the failover rules on the Reliability page.
A foreign operator will be able to read our citizens' data.
The platform underneath sees that a workload exists, how big it is and what it costs, not what is in it, and its operator actions are logged. For records no operator may read, Sealed keeps the data unreadable while in use and writes a receipt for your auditor.
Proofthe access table on the Security page and the SOC 2 Type II report under NDA.[2]
What does the Treasury pay, and when?
Hourly, at a published rate, with no minimum term and no commitment to size. Machines from $0.024 an hour; object storage $0.02 per GB a month. Tier A, for regulated data, is indexed at 115 against public cloud list price. On your own devices, the platform charge is quoted in writing.
Proofthe published rate card and the tier index, August 1, 2026.[3]
What does it cost to leave at the end of the term?
The outbound transfer rate, from $0.01 per GB, and nothing else. There is no exit fee. Because the machines, Kubernetes and the S3 API are standard, the next tender is not held captive by this one.
Proofthe transfer bands in the published pricing and the no-exit-fee clause in the agreement.[3]
Can one private cloud per agency really be kept apart from the next?
Each private cloud has its own private network, and nothing in it is reachable unless the agency publishes it. Tier A goes further: capacity reserved for one customer, vetted operator access and continuous control evidence, with a 99.99% uptime commitment.
Proofthe tier table, with isolation and uptime by tier, August 1, 2026.[4]
What happens when one site loses power?
Work restarts on another device you own inside your private cloud first. Pinned work moves only between the devices you named. Beyond that, across 1,800+ nodes only if you allow it. The Tier A commitment is 99.99%, about four minutes a month, in the master services agreement.
Proofthe uptime commitments on the Reliability page and the tier table.[4]
What can we put in front of the audit office?
A SOC 2 Type II report with an unqualified opinion, period November 1, 2025 to January 30, 2026, under NDA. An annual penetration test letter, under NDA. CMMC Level 2 is in progress. Sealed issues a receipt per run that records where it ran.
Proofthe attestation list on the Security page and the SOC 2 report under NDA.[2]
Who signs the contract, and under which law?
TripleXPOS LLC, a Wyoming company, holds the contract, the billing and the support. The platform underneath is named as a subprocessor in the agreement, and the list is available in writing. A local procurement partner you already know can sit in front of the contract.
Proofthe About page, the subprocessor list in writing and the agreement itself.
How does a ten-node pilot in one ministry begin?
Triple X connects ten devices at one ministry site to a private cloud, or lends hosted nodes while yours ship. Write the pass mark first: residency on named devices, a failover test with the power pulled, and a cost per workload below the last foreign quote.
Proofthe Contact page and a written quote from Triple X for your private cloud.
What is not included?
No published region list. No certification beyond the SOC 2 attestation, and no date for one. Accreditation for classified work is yours to obtain from your own regulator; the placement record helps, it does not replace it. GPU capacity is on quote. No data hall is built for you.
Proofthe attestation list on the Security page and the GPU answer on the Pricing page.
No questions under this term yet. Ask Triple X.