Isolated Spaces
Separate teams, services and environments inside Kubernetes.
SELF-HOSTED · POLICY-AWARE · ISOLATED
Every environment gets its own boundary.
Fugu Deck creates isolated Kubernetes Spaces with controlled access, explicit policies and a clear path from user to workload.
Request access or a demoaccess-control / live
Developer → staging-apiteam-alpha · read + deploy
APPROVEDContractor → production-dbno active policy
BLOCKEDSRE → productionbreak-glass · audited session
APPROVEDA system of clear boundaries.
Access, credentials and workloads follow one operating model instead of living in separate scripts, servers and chat messages.
Controlled access
Route connections through policy-aware layers and a secure gateway.
Visible changes
Keep infrastructure reproducible through Git and GitOps.
Infrastructure should explain itself.
Fugu Deck is a control layer for teams that need more than a server and a shared SSH key. It connects identity, policy, access and workload without hiding the path between them.
fugu-deck / system map
Control Planeusers · Spaces · state · workflows
COORDINATESKeyguardkeys · policies · sensitive operations
CONTROLSSSH Gatewaythe controlled path into an environment
ROUTESSpace Operatorisolated namespaces and workloads
ISOLATESThe useful question is not: is it running?
It is: who can reach it, through which boundary, with which policy, and what remains visible afterwards? Fugu Deck is built around that question.
IdentityWho is connecting?
PolicyWhat is allowed?
BoundaryWhich Space?
SessionWhat happened?
WorkloadWhat was reached?
Make every connection intentional.
Tell us what you are building and which environments you need to isolate.
Request access or a demo