Deployment
Cloud-managed and self-hosted deployment options for Basirah.
Basirah is available as a cloud-managed service or as a self-hosted deployment in your own infrastructure.
Cloud vs self-hosted
| Aspect | Cloud-managed | Self-hosted |
|---|---|---|
| Hosting | Managed by Synodician | Your infrastructure |
| Updates | Automatic, zero-downtime | You control the rollout schedule |
| Data residency | Synodician-managed infrastructure | Your network boundary |
| SSO/IdP | Configured via dashboard | Configured during setup |
| Compliance scoping | Synodician handles infra controls | Your team owns infra controls |
| SLA | 99.9% uptime | Depends on your ops |
Cloud is the fastest path to production. Choose self-hosted if your security policy requires data to stay within your network boundary, or if you need full control over upgrade timing.
Networking requirements
Basirah needs outbound HTTPS (port 443) to communicate with scanner APIs and ticketing systems. Allow outbound traffic to the vendor endpoints for whichever integrations you’ve enabled.
If you’re using bidirectional ticket sync (Jira, ServiceNow), Basirah also needs an inbound HTTPS endpoint reachable by your ticketing system’s webhook infrastructure.
Self-hosted deployment
Self-hosted installations are delivered as container images. Your account team will provide deployment guides, infrastructure requirements, and configuration details specific to your environment.
Contact your Synodician account team or reach out to sales for self-hosted deployment documentation, sizing guidance, and configuration support.