Platform engineering
Internal platforms
Give product teams self-service infrastructure while preserving operator controls. Bahriya replaces glued-together toolchains with a single platform that teams actually want to use.
Learn moreUse cases
Built for teams that ship globally
Bahriya is built for teams that need to provision fast, maintain control, and expose consistent platform workflows across engineering squads. From internal platforms to edge deployments, here is how teams use Bahriya.
Overview
Common use cases
Jump to any use case below for a detailed breakdown of how Bahriya helps.
Platform engineering
Internal platforms
Give product teams self-service infrastructure while preserving operator controls. Bahriya replaces glued-together toolchains with a single platform that teams actually want to use.
Organisation-level projects isolate teams with separate secrets, registries, and containers
Role-based access (owner, admin, member, viewer) at org and project level
Full activity log for every change across every resource — who changed what, when
API-first: everything in the console is an API call, so internal tooling hooks in cleanly
Console + CLI + API — three interfaces, one consistent platform
Edge compute
Edge container deployments
Deploy your full application to every region instead of proxying through a CDN or rewriting logic as edge functions. Any language, any framework — running close to your users with GeoDNS routing.
Deploy standard OCI containers to Helsinki, Virginia, Singapore, Falkenstein — more coming
GeoDNS routes each user to the nearest running instance automatically
No cache invalidation, no origin round-trips — every response generated locally
Autoscaling per region with independent sizing and resource controls
Add or remove a region with one config change — no infrastructure re-architecture
Multi-tenancy
SaaS environments
Run multi-tenant or customer-isolated workloads with explicit region and sizing controls. Bahriya gives SaaS operators the primitives to separate tenants cleanly without managing infrastructure directly.
Separate projects per customer or tier with independent quotas and secrets
Per-region deployment control — keep EU customer data in EU regions
Per-minute per-resource billing makes cost attribution per tenant straightforward
Private registries per project keep container images isolated
Scale each tenant independently — different CPU, memory, and replica configs
Release management
Staging and release paths
Mirror production profiles in lower environments for predictable rollout behaviour. Same regions, same resource shapes, same secrets structure — just different values.
Create staging projects that mirror production region and resource topology
Use the Reis CLI or API to automate promotion between environments
YAML-based infrastructure-as-code with reis apply for reproducible setups
Activity logs let you compare exactly what changed between deploys
Live pricing previews before you commit — no surprise cost differences
DevOps & SRE
Support and operations
Use activity history to diagnose changes and collaborate across teams quickly. Bahriya surfaces the context operators need without jumping between dashboards.
Unified activity log across containers, secrets, registries, and project changes
Track every deployment, scale event, and configuration change with timestamps
Role-based visibility — give support teams read access without exposing secrets
API-driven monitoring integration — pull activity data into your existing tooling
One console for the full picture: no context-switching between AWS sub-consoles
Ethical infrastructure
Values-aligned organisations
Businesses, NGOs, and organisations that make deliberate vendor choices can deploy on Bahriya knowing their infrastructure spend reaches no Israeli companies or their active supporters.
Every vendor in the stack vetted against a published ethical supply chain policy
UAE-based company operated by Mamluk LLC — not beholden to Silicon Valley
Infrastructure runs across Europe, Asia-Pacific, and North America
DNS, CDN, storage, CI/CD, and payment processing — all independently verified
A cloud provider you can deploy to with a clear conscience
From zero to deployed
One command. Every region.
Whether you use the console, the API, or the Reis CLI — deploying to multiple regions is a single operation. No infrastructure glue, no multi-step runbooks.
reis deploy
$ reis deploy --project web-app --region helsinki-1,virginia-1,singapore-1
Resolving container image...
Deploying to 3 regions:
helsinki-1 ████████████████████ deployed
virginia-1 ████████████████████ deployed
singapore-1 ████████████████████ deployed
TLS certificates issued.
GeoDNS records configured.
Health checks passing on all regions.
Live at: https://web-app.bahriya.cloud
3
Regions deployed
1
Command
0
Infrastructure glue
Map your use case to a working deployment path
Share your target architecture and we can help align it with Bahriya capabilities and roadmap. Managed services including caches, databases, and storage are planned for 2026/2027.