Every model executes the same LiquiFire Chains™ language. Integration contracts, API surface, and Chain behavior are identical across hosted, on-premise, and air-gapped environments.
Chains authored against the hosted service run without modification on any other model. There is no per-deployment variant and no migration rewrite.
When infrastructure requirements change, you re-point an endpoint. Development teams do not experience the transition.
Start fully managed and move to on-premise when the organization is ready. The cost of switching is one configuration change, not a project.
Who owns the infrastructure and who operates the software.
The fastest path from procurement to first render. LiquidPixels operates all infrastructure — no servers to provision, no environment to manage.
A private LiquiFire OS environment, dedicated to your organization, operated by LiquidPixels. No hardware procurement required.
LiquiFire OS deployed inside your own cloud tenancy. Retain full infrastructure ownership, or delegate day-to-day operations to LiquidPixels.
LiquiFire OS pre-installed on rack-ready hardware, deployed in your data center. LiquidPixels manages the software layer remotely. Each appliance runs independent Balancer, Render, and Storage nodes — scale throughput by adding Render nodes, add a second Balancer for HA/FO, or expand Storage without touching the rest of the configuration.
No network connection required at any point in the render path. No data leaves the environment — no telemetry, no licensing callbacks, no egress. Designed for classified and regulated environments where external connectivity is prohibited. Balancer, Render, and Storage nodes all run within the appliance. Updates via signed physical media.
On-premise deployments are not fixed configurations. Start with a single appliance or build a full data center topology with independent LiquiFire Balancer, Render, and Storage nodes. Each node type scales independently — multiple Balancer nodes provide HA/FO, additional Render nodes increase throughput, and multiple Storage nodes add redundancy. The architecture grows without a re-implementation.
Because all processing happens within your own infrastructure, rendered assets and source files never leave your controlled environment. This supports internal data recovery policies, data residency requirements, and compliance frameworks that prohibit confidential asset egress to external systems.
Answer four questions and we will surface the models most likely to fit your situation.
Preference or policy — not necessarily what exists today.
We work with your team to evaluate the full picture before making a recommendation.
Talk to an ExpertOperational and infrastructural differences. Chain language and capabilities are identical across all five.
| Hosted | Managed Hosting | Managed Appliance | Secure Appliance | Cloud License |
|
|---|---|---|---|---|---|
| Operated by LiquidPixels | Full | Full | Software only | No | Optional |
| Air-gapped / no outbound network | No | No | No | Yes | No |
| Data residency control | Region select | Full | Full | Full | Full |
| Elastic autoscaling | Yes | Yes | Hardware-bound | Hardware-bound | Yes |
| Time to first render | Days | 1–2 wks | 4–8 wks | 8–16 wks | 2–4 wks |
| Migration to on-premise | Supported | Supported | Already on-prem | Already on-prem | Supported |
Included with hosted service and managed hosting.
Named contacts, enhanced SLAs, and dedicated engineering access.
Remote software management for on-premise deployments.
The hosted service is production-ready in days and requires no infrastructure commitment. When requirements shift, the migration is an endpoint change — not a re-implementation.
Build Chains and complete integration against the hosted endpoint. No infrastructure procurement required.
Appliance delivery or cloud license provisioning runs concurrently with your integration work.
Update the base URL in your integration configuration. No application code changes required.
LiquidPixels offers OEM licensing for platform vendors, system integrators, and ISVs who want to deliver LiquiFire OS capabilities under their own brand. Engagements cover white-label licensing, custom development, bespoke network topologies, and configurations outside the standard models.
There is no self-serve path. The starting point is a conversation with our partnerships team to scope the engagement and identify the appropriate licensing structure.
Discuss OEM licensingWe work with your infrastructure, security, and procurement teams to scope the right model. Most organizations are in production on the hosted service within two weeks of signing.