System design
Flexible and Secure Architecture
Yarkon acts as a secure, high-performance web layer on top of S3-compatible storage — without modifying your data or storage backend.
Interactive DemoFlexible Deployment Models
Yarkon is available in two deployment models: Software-as-a-Service (SaaS) and Self-Hosted (Server).
Choose the model that best fits your organization's needs for control, compliance, and infrastructure management.
To learn more, see the Feature Comparison page.
Yarkon Software-as-a-Service
Fully managed Software-as-a-Service deployment.
- We handle all infrastructure management
- Automatic upgrades with zero downtime
- High availability, fully backed up
Yarkon Self-Hosted
Deploy Yarkon within your own VPC / network.
- Available both as EC2 AMI, or Docker image
- Deploy with any orchestration platform
- Full data sovereignty and compliance
System Diagrams
Simple setup for small teams and evaluation
- The most basic configuration
- Requires only a single EC2 / Docker
- ELB recommended for SSL termination
It is recommended to start with this configuration, and only upgrade to a more complex (and usually costlier) architecture as needed, or once your evaluation is complete.
Robust setup for mission-critical environments
- Multiple Yarkon instances behind a load balancer
- Automatic failover and redundancy
- Ideal for mission-critical applications
This configuration ensures that your Yarkon deployment remains operational even in the event of individual instance failures, providing peace of mind for critical business operations.
Optimized for high throughput and low latency
- Multiple Yarkon instances with optimized caching
- Load balancing for maximum performance
- Perfect for large teams with heavy usage
This configuration is designed to handle high traffic and ensure low latency for teams that have locations all over the world, where a CDN might be beneficial.
When using VPC endpoints buckets
- Required when using VPC endpoints buckets
- Yarkon Server works an in-VPC proxy
- Higher latency due to proxying
If you are using VPC endpoints buckets (better protecting your instances from internet traffic), you'd need this configuration. You can use it together with any of the other configurations. The image shows it used together with the basic configuration.