Deployment
Crawbl runs in your own infrastructure on any Kubernetes cluster.
Supported Platforms
| Platform | Status |
|---|---|
| Any managed Kubernetes | ✅ Supported |
| AWS EKS | ✅ Supported |
| Google GKE | 🔜 Planned |
| Azure AKS | 🔜 Planned |
| On-Premises | ✅ Supported |
Self-hosting gives you full data ownership, compliance with regional residency requirements, and predictable costs.
Infrastructure Requirements
Minimum (Dev/Test)
| Component | Specification |
|---|---|
| Kubernetes | Supported |
| Worker Nodes | 2 nodes, 4 CPU, 8GB RAM each |
| Storage | 50GB SSD per node |
| Database | Relational database, 2GB RAM |
| Cache | In-memory cache, 1GB RAM |
Production
| Component | Specification |
|---|---|
| Kubernetes | With HA control plane |
| Worker Nodes | 3+ nodes, 8 CPU, 16GB RAM each |
| Storage | 200GB SSD per node |
| Database | Relational database, 8GB RAM, replicated |
| Cache | In-memory cache, 4GB RAM, persistent |
Architecture Components
Click diagram to zoom
Deployment Process
Bootstrap Sequence
Click diagram to zoom
Required Secrets
Secrets are managed through an external secrets service and injected at runtime. No credentials are stored in code or configuration files.
GitOps Workflow
Click diagram to zoom
- Code is pushed to the main branch
- CI builds container images and updates tags in the deployment repo
- GitOps controller auto-syncs changes to the cluster
Monitoring
All components expose standard health and monitoring endpoints for orchestration and observability.
- Logging -- Structured JSON with correlation IDs
- Metrics -- Request latency (p50/p95/p99), error rates, resource utilization, LLM token usage
note
Contact us for deployment sizing guidance.