Content Portal · Deployment

Hosted, Private, or Self-Hosted

Three deployment models, one build. Run the portal as a hosted service, as a dedicated instance in your own cloud, or entirely on infrastructure you control — including restricted and disconnected environments.

Hosted SaaS
Operated by Shakewell
Shakewell runs the platform. You get an account, your content, and your users, with upgrades and operational monitoring handled for you.
Suits you when
- You want the shortest path from decision to live portal
- There is no requirement to keep content inside your own infrastructure
- You would rather not carry the operational load of another system
Single-tenant private cloud
Operated by Shakewell or your team
A dedicated instance, either in Shakewell's cloud or deployed into your own cloud account, with infrastructure defined in Terraform so the environment is reproducible rather than hand-built.
Suits you when
- Your data residency or isolation requirements rule out shared infrastructure
- You want the deployment inside your own cloud account and billing
- You need environment parity between staging and production for validation
Self-hosted
Operated by Your team, with support from Shakewell
The full stack runs on infrastructure you control, containerized end to end. Suitable for restricted networks and environments with limited or no external connectivity.
Suits you when
- Content cannot leave your network under any circumstances
- The environment is restricted, disconnected, or air-gapped
- Your own operations team will run and monitor the platform

The same product in every model
There is no reduced edition. The application is containerized and its infrastructure is described as code, so the version that runs as hosted SaaS is the version that runs inside your network. That matters at procurement time, because it means the deployment model is a hosting decision rather than a feature trade-off.
Releases without downtime
Deployments follow a blue-green pattern: the new version comes up alongside the old one and traffic switches once it is healthy, with the previous version still standing if it is not. For an operation where maintainers depend on the library during a shift, an upgrade window is a real cost.
Moving between models
Starting hosted and moving self-hosted later is a supported path rather than a migration project, because the artifact is the same. It is worth asking any vendor this question early — the answer tells you how much leverage you are giving up on day one.

Also in This Section