Skip to main content

About the iCommerce embedded engine

This explanation covers the local-first iCommerce engine and how deterministic APIs make automation safe.

How the engine works

  • The embedded engine runs in-process on SQLite or PostgreSQL.
  • Deterministic operations require explicit write intent.
  • Language bindings expose a unified API surface.

Why this design

Local-first execution improves latency and reliability while keeping behavior predictable.

When to use it

  • Agent workflows: safe, deterministic operations
  • Edge deployments: local-first execution
  • High-throughput: in-process calls with minimal overhead

Further reading