Keystone holds a proprietary technology platform — built by yGen, deployed by yForce, operated inside Clicktek engagements, and engineered for institutional buyers who need sovereign AI without compromise. Three components: Phoenix the agent runtime, AI Box the sovereign appliance, yForce the architects who stand it all up. Together, the sovereign agent stack the group goes to market with across APAC.
The platform is built and operated from Manila. The institution that contracts for it sits in Singapore. Most regional consultancies blur where the contract lives and where the work happens — Keystone is explicit about both. The structure is calibrated for the questions enterprise procurement, regulators and institutional capital actually ask.
The holding entity is domiciled in Singapore — the institutional jurisdiction of choice across APAC for capital, contracting, audit posture and cross-border regulatory clarity.
Investor relations, master contracting and group governance flow through Keystone Apex Holdings Pte Ltd. This is the entity counterparties transact with where the structure of the engagement matters as much as the work.
The platform is built in Manila. yGen engineers Phoenix and AI Box. yForce architects deploy them into client environments. Clicktek delivery teams operate them inside live engagements. The whole stack lives within walking distance of itself.
Manila is the engine room — where the platform is engineered, hardened, and run. The talent depth that lets the platform scale is concentrated here by design, not as cost arbitrage.
Three components, engineered by the group, designed to be deployed together. The runtime that the agents live inside. The sovereign appliance the runtime can run on. The architects who stand the whole thing up inside an enterprise. Each is independently useful. Together they are a platform institutional buyers can actually procure.
Most AI workflow tools make you script every decision. Phoenix is different — the canvas is configuration, the LLM is the execution engine. It decides at runtime which specialist to call, which tool to use, which skill to run. Multi-agent teams, sandboxed Docker per session, persistent memory and built-in RAG, multi-channel deployment.
The cloud is not where AI has to live. AI Box is a self-contained appliance running local LLMs at production speed — deployed in days, operated on fixed cost, owned outright. For regulated industries, sovereign-data buyers, and operators who want the OpEx curve to stop pointing the wrong way, AI Box is the body Phoenix can run inside.
Software alone does not ship AI. yForce is yGen's AI Architecture Division — four disciplines, one delivery team. They scope the use case, design the system, engineer the agents, ingest the data, deploy the platform, and stay to operate it. Build, Deploy & Operate, or Co-build engagement models.
A clean architectural picture of where each component sits and what it provides. Buyers can adopt one, two, or all three — but the design is for all three to compose into a single sovereign agent platform inside the enterprise, with Clicktek operating it in production.
Where does the contract live, where does the platform live, who indemnifies, which jurisdiction governs disputes. Singapore holding contracts. Manila operating subsidiaries deliver. The data sits where the buyer chooses — including inside their own walls on AI Box.
One holding, one technology platform, one operating standard. Audit and risk functions can pass the structure through committee without bespoke carve-outs. Sovereign deployment options eliminate the cross-border data questions that derail most cloud-AI procurements.
For multi-subsidiary engagements — yGen builds the platform, yForce stands it up, Clicktek runs the operations — the buyer transacts with Keystone once, escalates once, and reports out once. No vendor-management overhead masquerading as a partnership.
Cloud-token bills compound with usage. AI Box is a fixed-cost asset. Phoenix is owned, not rented per seat. yForce is a delivery team, not an SI markup on someone else's stack. The platform was designed so the cost curve flattens as the operation scales — not the opposite.
For multi-subsidiary engagements — where the platform, the deployment, and the operations all need to ship together — Keystone is the prime. Operating subsidiaries are named delivery entities under the same master agreement, each with their own scopes, deliverables and acceptance criteria. The buyer transacts with one institution. The operating companies remain accountable for what they ship.
Where the conversation is the platform, the architecture, or a multi-subsidiary engagement — Keystone is the right counterparty. Where the conversation is product detail or sales, yGen and Clicktek take it from here. Either way, we route from a single 30-minute call.