Self-hosted credential broker
Run the credential broker inside infrastructure you control.
Teams with data-location, network, or operational-control requirements can deploy Shortspan themselves. The same web console, API, and Go CLI remain available, while your team owns the application environment, database, root encryption key, backups, upgrades, and monitoring.
Why teams change
Control of the deployment includes responsibility for it.
Self-hosting can keep the broker close to private infrastructure and place storage under your organization’s account. It can also satisfy requirements that a hosted service cannot address. But it moves availability, key custody, backups, patching, TLS, and incident response onto your operators.
Shortspan documents the runtime requirements, installation path, security-sensitive configuration, upgrade procedure, and ongoing operations. The root key used to wrap workspace master keys is deliberately separate from the Laravel application key and must be backed up and protected as production key material.
What Shortspan adds
Control around the workflow, not another workflow beside it.
Your hosting boundary
Operate the Laravel application, database, cache, queue workers, and public endpoints in the environment and region you select.
Explicit encryption key custody
Generate and protect the Shortspan root key that wraps workspace master keys, with documented rewrapping and recovery considerations.
Documented upgrade path
Use the self-hosting operations and upgrade guides to keep the application, workers, scheduler, CLI releases, and schema in a supported state.
The workflow
From registered resource to accountable use.
- 01
Review requirements
Plan PHP, database, queue, cache, TLS, DNS, backups, mail, monitoring, and key-management responsibilities before deployment.
- 02
Install and configure
Deploy the application, create the root encryption key, run migrations, start workers and scheduling, and verify the public surfaces.
- 03
Operate and upgrade
Monitor health, retain tested backups, rotate operational credentials, and follow the documented upgrade sequence for each release.
Operational outcomes
Make the secure path the understandable path.
- Control over the application and data hosting region
- Direct ownership of encryption key custody and backups
- Network placement close to private infrastructure
- The same CLI-first workflow as the hosted product
Common questions
Know where the boundary is.
- Is self-hosting maintenance-free?
- No. Your team owns deployment security, availability, database operations, backups, queue workers, scheduling, monitoring, upgrades, and root-key recovery.
- Is the Shortspan root key the same as Laravel APP_KEY?
- No. They are deliberately separate. The Shortspan root key wraps workspace master keys and must be generated, stored, and backed up as distinct production key material.
- Can the documentation be hosted on the same domain?
- The application supports dedicated documentation and status hosts as well as path-prefix fallbacks for environments where multiple hostnames are inconvenient.
Read the implementation details
Documentation for this workflow
Related solutions
Connect the next part of the workflow
Start with one project and one access problem.
Create a workspace free, or tell us what your team needs to broker, approve, and review.