Map the environment
Understand the available hardware, data boundaries, workloads and governance requirements before choosing a deployment shape.
Citadel · Deployment
Citadel is designed to meet organisations where their infrastructure already lives—on-premise, in a private cloud, or across a controlled hybrid fleet.
Choose your environment ↓
Build a deployment sketch
Tell us where data must stay, which compute is available and where users work. The configurator will assemble an illustrative deployment pattern.
A measured path
Private infrastructure should be introduced deliberately. The deployment path begins with the environment and grows from evidence.
Understand the available hardware, data boundaries, workloads and governance requirements before choosing a deployment shape.
Select appropriate models, inference engines and compute tiers, then define how prompts should move through the system.
Introduce Citadel inside the controlled environment and validate it against a focused, measurable use case.
Monitor the fleet, model behavior and capacity as requirements change—without giving up control of the stack.
The control boundary
Models can change. Hardware can scale. Workloads can evolve. The important boundary remains the same: prompts, context and organisational data do not need to leave the environment you control.
Explore governance →The next question