Scale your PDF infrastructure horizontally. Active-active request processing, database-backed sessions, distributed job queues, and intelligent leader election — all without sticky sessions.
HTTPS Termination · Health Checks · Round-Robin
HTTP + Queue + Hot Folder + Alerts
HTTP + Queue (Hot Folder standby)
Sessions · Queue · Leader Election
NFS / SMB · AES-256 Encrypted
All YesPDF instances simultaneously process incoming HTTP requests. No sticky sessions needed — the load balancer distributes using round-robin or least-connections.
| Capability | Mode | Details |
|---|---|---|
| PDF Tools (merge, split, rotate, compress) | ✔ Active-Active | Any instance handles any request |
| OCR Processing | ✔ Active-Active | CPU-intensive jobs distributed across all instances |
| Document Conversion (Word, Excel, HTML, CAD) | ✔ Active-Active | Concurrent processing on all nodes |
| Digital Signature | ✔ Active-Active | Sign/verify from any instance |
| Web Viewer & Editor | ✔ Active-Active | Stateless rendering, works from any node |
| File Upload / Download | ✔ Active-Active | Shared storage ensures file availability |
| REST API (v1) | ✔ Active-Active | Stateless API with shared session validation |
No Sticky Sessions Required. User sessions are stored in PostgreSQL — a user can log in through Instance A and seamlessly continue on Instance B without re-authenticating.
Every component designed for multi-server deployments from the ground up.
Sessions stored in PostgreSQL, not server memory. HTTP-only Secure cookies, single-session enforcement, idle timeout, and activity throttling to minimize DB writes.
Atomic database locking (SELECT ... FOR UPDATE SKIP LOCKED) ensures each job is processed exactly once. Configurable concurrency limits and automatic stale job recovery.
Database-based leader election for hot folder signing. Automatic failover in ~30s. Graceful handoff on shutdown. No Redis or ZooKeeper required.
Rate limiting state stored in database, enforced globally. API rate limits, login lockout, IP restrictions — all synchronized across nodes.
GET /api/health returns 200 OK for load balancer integration. Automatic traffic routing away from unhealthy instances.
Double-submit cookie pattern requires no server-side state. Works perfectly in multi-server environments without session affinity.
Choose the deployment mode that matches your availability requirements. Scale horizontally by simply adding worker instances.
Standard deployment for small to mid-size organizations. One YesPDF instance handles everything.
Recommended for production. Fault tolerance with automatic failover for zero downtime.
High-throughput environments. Add worker instances as demand grows.
All settings managed through environment variables. No complex XML or YAML files.
| Setting | Default | Description |
|---|---|---|
INSTANCE_ROLE |
primary | primary runs all background daemons; worker runs HTTP + queue only |
SERVER_ID |
auto-detect | Unique identifier per instance (leader election & session tracking) |
DATABASE_URL |
sqlite:///./yespdf.db | Must be PostgreSQL for multi-server deployments |
UPLOAD_DIR |
./uploads | Must be shared storage (NFS/SMB) for multi-server |
TRUSTED_PROXIES |
empty | Load balancer IP(s) for correct client IP detection |
SESSION_COOKIE_SECURE |
False | Set to True when NLB terminates HTTPS |
QUEUE_MAX_WORKERS |
8 | Total concurrent workers per instance |
QUEUE_MAX_OCR |
2 | Max concurrent OCR jobs per instance |
Every failure scenario has been engineered with automatic recovery. Know exactly what happens when things go wrong.
Standard enterprise infrastructure. No exotic dependencies or third-party services required.
Built-in monitoring tools give you real-time insight into every node.
Load balancer integration with automatic routing.
Real-time system stats, active users, storage usage, operation counts, per-user breakdowns, and filterable audit logs — all accessible from the web admin panel.
Operation counts, trends, and per-user breakdowns. Filter by date range, user, or category.
Complete trail of all operations with user identity, IP address, and timestamp. Centralized in shared DB.
In-app alerts for certificate expiry, storage thresholds, job failures, and system health warnings.
Each YesPDF instance requires a valid license file bound to the server's hardware fingerprint. Contact your YesPDF representative for multi-server licensing options.
One license, full functionality. SQLite or PostgreSQL. Ideal for small teams.
Two licenses for primary + worker. PostgreSQL required. Recommended for production.
Volume licensing for 3+ nodes. PostgreSQL + shared storage. Custom SLA available.
Enterprise PDF management, on your infrastructure. No cloud. No limits.
YES BILISIM TEKNOLOJILERI YAZILIM DANISMANLIK SAN. VE TIC. A.S.