Skip to main content

​
What It Does

Beyond databases and APIs, your application needs infrastructure services: message queues for async processing, object storage for files, caches for performance, API gateways for routing, and more. Monk detects these needs during code analysis, then provisions and configures them automatically. Like databases, you choose how they’re deployed: self-hosted, cloud managed, or third-party services. Monk handles provisioning, connection strings, and wiring.

​
How It Works

​
Automatic Service Detection

During code analysis, Monk identifies infrastructure service requirements: What Monk discovers:
  • Message queue usage (RabbitMQ, Kafka, SQS clients)
  • Object storage references (S3 SDK, MinIO client, file uploads)
  • Caching layers (Redis client, Memcached usage)
  • API gateway requirements
  • Web server needs (Nginx, Apache configuration)
Monk understands your infrastructure needs before you configure anything.

​
Flexible Deployment Options

Once Monk knows which services you need, it offers deployment options:

​
Option 1: Self-Hosted in Containers

Best for: Development, staging, full control, cost optimization
  • Services run in containers on your infrastructure
  • Monk handles setup, persistence, and configuration
  • Quick to spin up, easy to tear down
  • Examples: MinIO for object storage, RabbitMQ for queues, Redis for caching

​
Option 2: Cloud Provider Managed Services

Best for: Production, simplified operations, automatic scaling
  • Uses cloud provider’s managed services
  • Examples: AWS S3/SQS, GCP Cloud Storage/Pub-Sub, Azure Blob/Service Bus
  • Automatic backups, updates, high availability
  • You provide cloud credentials, Monk provisions and configures

​
Option 3: Third-Party Managed Services

Best for: Specialized features, global distribution, multi-cloud
  • Uses specialized service providers
  • Examples: Cloudflare R2 (storage), Redis Cloud (caching), specific SaaS platforms
  • Often have free tiers or pay-per-use pricing
  • Advanced features like global distribution
Progression examples: Object Storage:
  • Start with MinIO (containerized) for development
  • Move to DigitalOcean Spaces or AWS S3 for production
  • Scale to Cloudflare R2 for global CDN + storage
Message Queues:
  • Start with RabbitMQ (containerized) for development
  • Move to AWS SQS or managed RabbitMQ for production
  • Scale to Apache Kafka for high-throughput event streaming
Caching:
  • Start with Redis (containerized) for development
  • Move to AWS ElastiCache or managed Redis for production
  • Scale to Redis Cloud for global, multi-region caching
The choice is yours. Monk recommends the best option based on your stage, scale, and requirements.

​
Supported Essential Services

Monk supports 50+ essential services out of the box via integrations: Message Queues & Brokers:
  • RabbitMQ
  • Apache Kafka
  • AWS SQS
  • Eclipse Mosquitto (MQTT)
Object Storage:
  • MinIO (S3-compatible)
  • AWS S3
  • DigitalOcean Spaces
  • Cloudflare R2
  • IPFS (decentralized)
Caching:
  • Redis
  • Memcached
  • Hazelcast (in-memory data grid)
API & Gateway:
  • Kong API Gateway
  • Hasura GraphQL Engine
  • AWS API Gateway
Service Discovery & Config:
  • HashiCorp Consul
  • etcd
  • Apache ZooKeeper
Web Servers & Proxies:
  • Nginx
  • Apache HTTP Server
  • HAProxy (load balancer)
Security & Secrets:
  • HashiCorp Vault
  • Keycloak (identity/auth)
  • Vaultwarden (password manager)
Monitoring & Observability:
  • Prometheus + Grafana
  • ELK Stack (Elasticsearch, Logstash, Kibana)
  • Fluent Bit (log processing)
  • TIG Stack (Telegraf, InfluxDB, Grafana)
  • Graphite
  • LibreNMS
DevOps & CI/CD:
  • Jenkins
  • GitLab
  • JFrog Artifactory
  • Sonatype Nexus
  • SonarQube
Data Integration & ETL:
  • Airbyte
  • Apache Airflow
  • Jitsu
Communication & Collaboration:
  • Mattermost (team chat)
  • Chatwoot (customer engagement)
CMS & Content:
  • WordPress
  • Drupal
  • Strapi (headless CMS)
  • Directus (data platform)
  • DokuWiki
Analytics & BI:
  • Metabase
  • Apache Superset
  • Trino (distributed SQL)
Automation:
  • n8n (workflow automation)
Big Data:
  • Apache Hadoop
AI/ML Serving:
  • Ollama (local LLMs)
  • OpenLLM (LLM serving)
  • TensorFlow
Other Infrastructure:
  • CoreDNS (DNS server)
  • BIRD (BGP routing)
  • Gost (tunnel/proxy)
Don’t see your service? Check Integrations for the full list, or let us know - Monk’s integration ecosystem is constantly growing.

​
Automatic Connection Management

Monk generates and manages connection strings and credentials automatically via Configuration & Wiring: What Monk handles:
  • Connection string generation (message queue URLs, storage endpoints, cache URLs)
  • Credentials creation and secure storage
  • Network configuration for service access
  • Authentication setup (API keys, tokens, certificates)
  • Service discovery registration
The benefit: Switch between deployment options without code changes. For example, move from self-hosted MinIO to AWS S3, and Monk updates your application’s storage configuration automatically - your code using the S3 SDK continues working without modification.
Data migration between service providers is not yet automated. When switching from self-hosted to managed (or vice versa), Monk updates connection strings but doesn’t transfer existing data automatically. You’ll need to migrate data manually or wait for automatic data migration (coming soon).

​
Service Configuration

Monk can configure service settings to match your requirements: Configurable settings:
  • Message queue sizes and retention policies
  • Storage quotas and access policies
  • Cache memory limits and eviction policies
  • API gateway rate limits and routing rules
  • Service discovery health checks
  • Monitoring thresholds and alerts
Ask Monk to adjust any service setting - it understands service-specific parameters for each supported service type.

​
Coming Soon

Several essential service features are actively in development: Data Migration COMING SOON
  • Automatic data transfer when switching providers
  • Queue message migration
  • Object storage bulk transfers
  • Cache warming on provider switch
Advanced Monitoring COMING SOON
  • Queue depth monitoring with auto-scaling
  • Storage usage alerts
  • Cache hit rate optimization
  • Service health dashboards
Custom Management Actions COMING SOON
  • One-command service operations
  • Performance diagnostics
  • Runbook automation for common tasks

​
What Makes This Different

Traditional infrastructure service setup requires:
  • Choosing between managed services and self-hosting manually
  • Learning cloud provider service consoles
  • Writing connection configurations and managing credentials
  • Configuring service-specific settings
  • Updating application configs when changing providers
  • Managing multiple service types with different tools
  • Setting up monitoring and alerts manually
With Monk: Say what services you need (or let Monk detect them). Choose deployment option. Done.

​
Key Capabilities

  • Automatic detection - Identifies service requirements from code
  • 50+ services supported - Message queues, storage, caching, gateways, monitoring, and more
  • Flexible deployment - Self-hosted containers, cloud managed, third-party managed
  • Smart recommendations - Monk suggests best option for your use case
  • Connection string management - Automatic generation and updates
  • Easy switching - Move between deployment options without code changes
  • Service configuration - Adjust settings via natural language
  • Multi-service applications - S3 + RabbitMQ + Redis + Vault? No problem
  • Secure credential handling - Service credentials stored securely