Commercial Contract
Engula Enterprise
Enterprise-grade deployment for large-scale Redis workloads
Larger-scale production deployments
For production scenarios that exceed the natural boundaries of the Developer Edition, with support for more nodes, more business lines, and more complex capacity planning.
A clear enterprise service channel
A commercial contract spells out the license scope, service levels, upgrade path, and support entry point, so production issues have a clear owner and handling process.
Migration and long-term evolution support
Covering architecture review, PoC validation, shadow-traffic cutover, version upgrades, and roadmap alignment to reduce the uncertainty of migrating off Redis.
Edition Comparison
Data-path features (protocol / replication / failover / ACL / TLS / memory compression / RDB acceleration) are fully identical across the two editions; Enterprise additionally provides paid scale-out capabilities and commercial commitments.
| Dimension | Engula Developer Edition | Engula Enterprise |
|---|---|---|
| Positioning | Development / testing / PoC / teaching / small-scale production | Medium-to-large production / business-critical workloads / compliant deployments |
| Pricing | Free | Per Order Form (contact Sales for a quote) |
| Capacity limit | 6 Engula nodes | Per Order Form (unlimited nodes by default) |
| Per-instance memory | Unlimited | Unlimited |
| Cluster topology | Full (Standalone / Replication / Cluster, with no limit on the master/replica ratio) | Full (identical to Developer Edition, with no node limit) |
| Data-path features | Full (read / write / replication / backup / restore / failover / rolling upgrade / disaster recovery) | Full (identical to Developer Edition) |
| Kernel optimizations | Full (RDB speedups, memory compression, TCO optimization) | Full (identical to Developer Edition) |
| Logging & monitoring | Standard (INFO / SLOWLOG / metrics integration) | Standard (identical to Developer Edition) |
| License Key | Not required | Required (issued by Sales) |
| Production-use license | Allowed (subject to the 6-node capacity limit) | Allowed (no capacity limit) |
| 商业支持 | 无 | 按订单表约定 |
| Compliance materials | Not provided | Provided per Order Form |
| Architecture review / incident response | Not provided | Per Order Form |
| Upgrade to Engula Enterprise | Contact Sales to have a License Key issued | — |
ROI
Memory cost-savings estimate
A rough estimate based on your current Redis physical-memory footprint and machine cost. The result is not a quote; actual savings depend on data structures, value sizes, key counts, and deployment topology.
Defaults assume ¥100,000/year per 256 GB machine and a 50% memory saving. Adjust the inputs to your procurement pricing and actual ValueSight results.
Enterprise Support
Enterprise support commitments
Response time, temporary workarounds, root-cause fixes, security-patch delivery, service hours, escalation channels—response tiers are set by contract.
Tiered support plans
Specific service levels are set by contract
Fast security-patch delivery
Higher-severity vulnerabilities get faster response
Public security advisories
Engula publishes security advisories including temporary mitigation guidance
Performance & Reliability · Verified
Measured numbers: Engula vs Redis
The table below is a fixed release baseline, convenient for review and reuse in sales materials; for the latest live results, test versions, and hardware configuration, see the live proof page.
| Metric | Redis 7.2.11 | Engula 2.2.0 |
|---|---|---|
| BGSAVE wall-clock | 50.86s | 3.71s (13.7× faster) |
| RSS growth during BGSAVE | +50–80% | +25% |
| Single-machine capacity utilization ceiling | ~50% | ~75% |
| RDB save | 20.97s | 2.12s (9.9× faster) |
| RDB load | 14.62s | 2.39s (6.1× faster) |
RDB save/load above are single-point string/8GB measurements; the full matrix covers string/hash/set × 1–8GB and speedup varies by data type and size (SAVE peaks at 11.3× for string/4GB). Baseline: Redis 7.2.11.
Anonymized Cases
Anonymized production scenarios
The cases below are presented anonymized by industry, workload profile, and benefit metrics; specific customer names are withheld per contract.
Production case
Real-time fraud detection · Fintech
Memory −74%
601.6 GB → 153.6 GB; billions of keys, average value < 256 bytes, high-frequency mixed read/write load. Cut over to the primary instance after 2 weeks of shadow-mode validation.
Production case
Recommendation-engine cache · Video & Entertainment
Memory −43%
Hundreds of instances, dominated by Hash and ZSet. The 7.7 TB of memory saved translated directly into deferrable capacity-expansion purchases.
Production case
Message-stream system · E-commerce
BGSAVE 45s → 8s
RDB recovery dropped from 90s to 12s (partly due to the reduced data volume after the memory savings). Shorter maintenance windows mean less business disruption.
Contract & Licensing
Contract-based licensing, contract-based engineering delivery
Engula sells software licenses and customers self-deploy. The following contract elements and data-plane commitments are written into the EULA and the sales contract.
Contract signing
Sign a formal contract with Sales, specifying the license term, capacity limit, and service level.
License activation
A local license file activates the product once placed in the Engula data directory.
System-integrator deployment rights
Third-party system integrators may deploy in the licensee’s data center / controlled infrastructure; see the EULA for details.
Short-term contracts
30 / 60 / 90 days, suitable for large-scale validation or temporary projects; fully equivalent to long-term contracts at the engineering layer.
Data-plane Commitment
The data plane stays fully functional after expiry
After the contract / license expires, data remains readable and writable, and replication and failover are unaffected. Control-plane operations such as cluster-topology changes resume after renewal.
One-on-one pricing by node scale, with the customer’s net savings as a precondition
Ready to begin your Enterprise deployment?
Contact Sales for a quote or to schedule a technical alignment meeting; you can also validate with the Developer Edition first, then proceed through the commercial process.