Indi GupteProfileBriefDashboardMeet page

SpaceComputer: the factory infographic

securitySingaporeat Web Summit: startup (growth)our decision: meet, priority 2

Confidential computing, keys and attestation for cloud and AI workloads, up to satellites.

1

What the company does

SpaceComputerConfidentialcomputing and keymanagementAttestation andzero trustCloud, AI andspace systems

In normal terms

Cybersecurity company building confidential computing, key management, attestation and zero-trust services for cloud and AI workloads, extended to satellites and space systems.

SpaceComputer builds confidential computing, key management, attestation and zero-trust services for cloud and AI workloads, extended to space systems.

In lay terms

SpaceComputer builds locked rooms for computer work, with proof that nobody peeked, even on satellites.

2

The risks it faces, especially from AI agents

Locked room,wide reachKeys foragentsAttestingbehaviourAgent risks forSpaceComputer

In normal terms

  • Locked room, wide reach. An agent in a confidential environment can still reach and act on outside systems.
  • Keys for agents. Agents holding keys can use them beyond their task.
  • Attesting behaviour. Attestation proves what code runs, not whether its actions were authorised.

In lay terms

  • Locked room, wide reach. The room is locked, but the worker inside has a phone.
  • Keys for agents. A robot with a key ring.
  • Attesting behaviour. Proof of who is in the room, not of what they did.
3

How RiskMandate helps

Reachwhat it can touchMandatewhat it may dothe Gap
  1. Reachwhat it can actually access or affectWhat the attested agent can still reach outside.
  2. Mandatewhat the business authorisedWhat it was authorised to do.
  3. Gapthe difference: the riskActions attestation does not cover.
  4. Barrierswhat really stands in the wayAttestation and key controls as evidence.
  5. Provenancewho owns it, who reviewed it, which versionAttested version, owner and reviewer.

In normal terms

Attestation proves which agent is running; a behaviour policy says what it may do. Together they make a verifiable agent. Shared ground with sgit on keys and verifiable trust.

In lay terms

SpaceComputer proves who is in the room; RiskMandate says what they are allowed to do there.

A first line for the conversation: You prove which code is running. We say what it may do. Together: a verifiable agent.

Sources and method

The facts in grey (what it does) are from the company map, which cites:

  • websummit.com, read 2026-11-01: LIS26 appearance page: name, country, industry, website
  • websummit.com, read 2026-11-01: listed on the 2026 featured startups list with its elevator pitch (the "what" field)

The risks and how RiskMandate helps are our analysis, written by dev@web-summit.indi on 3 November 2026 from those facts and RiskMandate's model as this site explains it (Reach, Mandate, Gap; an Agent Behaviour Policy in practice). They are not the company's own statements and name no incident. A person reviews each before it is used.

All the factory's companies

For an agent: this page is https://web-summit.sgit.ai/people/indi/factory/spacecomputer/index.html (markdown: https://web-summit.sgit.ai/people/indi/factory/spacecomputer/index.md). Site index for agents: https://web-summit.sgit.ai/llms.txt. Source: https://github.com/SGit-AI/SGit-AI__Website__Web-Summit (release branch dev). Identity of the agent that runs this site: https://web-summit.sgit.ai/agent/index.html.