Context Engine gives teams a live context layer where scoped memory, rules, triggers, and event-driven orchestration work together. Instead of stitching a database, cache, vector store, and workflow logic by hand, you get one runtime for contextual continuity and adaptation. Start in Community Edition for fast pilots and single-node production, then move to Enterprise when you need scale, compliance, and operational guarantees.
Context Engine works with your databases, brokers, and workflow tools—but solves a different problem: maintaining shared contextual state and reacting to changes across scopes, actors, and systems.
Databases store records. Context Engine maintains scoped relationships, continuity, and policy-aware transitions as state evolves.
Vectors help retrieve meaning. Context Engine combines retrieval with active rules, timelines, and triggerable decisions.
Workflow tools run steps. Context Engine keeps shared memory and conditions consistent across many workflows and actors.
Buses move messages. Context Engine interprets events against live context so every event can produce context-aware actions.
Core is generic, but we ship opinionated helpers for common architectures. Like Redis for caching, Context Engine has its killer patterns.
Publish actorless workflows with goal + context + required capabilities to a shared Task Board. Services subscribe and atomically claim tasks if their capabilities match. No hardcoded routing.
View SDK helper →Merge sensor streams into live position map. Used by Robo Assistant for fleet/warehouse.
Long-running workflows with compensations.
All layers in Robo Meister share one Task Board. Robo Connector publishes actorless business goals. FlowBeacon AI (AI Network) and Robo Assistant (LAN/Fleet) claim tasks based on capabilities.
[Robo Connector publishes goal] -> [Context Engine = Task Board: goal + context + capabilities] -> [FlowBeacon AI claims AI tasks, Assistant claims physical] -> [Result + telemetry back to CE]
// Publisher
await ce.board('business-goals').publish({
goal: 'process-invoice',
context: { tenantId: 'acme' },
capabilities: ['ocr','accounting:post'],
payload: { invoiceUrl: 's3://...' }
})
// Subscriber - FlowBeacon AI
await ce.board('business-goals').claim(
{ capabilities: ['ocr'] },
async (task) => {
const result = await aiNetwork.run(task)
await ce.board('business-goals').complete(task.id, result, { cost: 0.02 })
}
)# Publisher
await ce.board('business-goals').publish({
'goal': 'process-invoice',
'context': {'tenantId': 'acme'},
'capabilities': ['ocr', 'accounting:post'],
'payload': {'invoiceUrl': 's3://...'}
})
# Subscriber - FlowBeacon AI
async def handle(task):
result = await ai_network.run(task)
await ce.board('business-goals').complete(task.id, result, {'cost': 0.02})
await ce.board('business-goals').claim({'capabilities': ['ocr']}, handle)Under the hood: 3 Lua scripts executed atomically in Redis — board_publish.lua, board_claim.lua, board_complete.lua — via Java API /board/{board}/publish|claim|complete. C microserver unchanged.
Use Context Engine when decisions depend on evolving state across systems—not just isolated events or static records.
Maintain shared memory across agents, tools, and approval steps so outputs remain coherent over long-running tasks.
Trigger policy-aware path changes when risk, regulations, or customer status shifts mid-process.
Drive automation from contextual state transitions instead of brittle point-to-point if/else integrations.
Convert event streams into durable operational context that supports investigation, replay, and controlled remediation.
Keep state synchronized across apps, APIs, humans, and devices with scoped context propagation.
Coordinate physical and digital signals with memory-aware rules for adaptive field behavior and exception handling.
Robo Meister is the biggest production implementation of Task Board pattern. Like Redis is a data structure server but won with caching helpers, and Elasticsearch is Lucene but won with search() — Context Engine is a context-native runtime but wins with Task Board pattern.
Company / Internet — Defines 90% of main workflows, publishes actorless goals to CE Task Board.
Explore Robo Connector →AI Network — Orchestrates AI resources, claims tasks requiring OCR, classification, voting. Formerly /solution/ai-module, now at ai.robo-meister.com.
Explore FlowBeacon AI →LAN / Fleet / Digital Twin — Local LAN via Hub/Router, fleet management, position mapping and sensor merge into digital twin map.
Community Edition is ideal for adoption, experimentation, and single-node production. Enterprise adds the operational guarantees needed when your context layer becomes core infrastructure.
Elastic sharding, consensus replication, automatic failover, and rolling upgrades that keep contextual decisions online.
SSO, KMS, tamper-evident audit, retention policies, and legal hold for regulated context flows.
Route semantic and key-based queries across shard-local indexes with hybrid BM25+ANN ranking and freshness controls.
Tiered storage with S3/GCS offload, PITR backups, and cross-region DR for mission-critical contextual continuity.
Perfect for dev, pilots, and single-node production.
For teams that need scale, compliance, and SLA.
| Capability | Community | Enterprise | Notes |
|---|---|---|---|
| APIs & SDKs (JS/Python/PHP/Go) | ✅ | ✅ + batching/multiplex | SDKs Apache-2.0 |
| KV + Vector index (HNSW) | ✅ | ✅ + distributed/hybrid | Hybrid BM25+ANN routing in EE |
| Rules & triggers, webhooks | ✅ | ✅ + DAG/compensations | Orchestration in EE |
| Admin UI | ✅ (essentials) | ✅ + inspector & replay | Policy editor in EE |
| Clustering, sharding & consensus replication | — | ✅ | HA + RAFT, rolling upgrades |
| Zero-downtime upgrades | — | ✅ | |
| Tiered storage & cloud offload | Basic snapshots | ✅ (S3/GCS, lifecycle) | Hot/warm/cold tiers |
| RBAC | ✅ | ✅ + ABAC | Row-level scopes |
| TLS & at-rest encryption | ✅ | ✅ + BYOK/KMS | Key rotation in EE |
| SSO (SAML/OIDC) | — | ✅ | |
| Audit & lineage | Basic logs | ✅ (tamper-evident) | Retention & legal hold |
| Data residency / air-gapped | — | ✅ | |
| Backups | Manual snapshots | ✅ (PITR + scheduled) | |
| Disaster recovery | — | ✅ (cross-region) | |
| Connectors | Postgres, HTTP, Files | + Kafka, S3/GCS, Snowflake, Elastic, Dynamics, SAP | Packs available |
| Metrics | Prometheus (basic) | Dashboards & SLOs | OTel tracing in EE |
| Offline cache & sync | Basic | CRDT/OT merges | Selective sync |
| Support | Community | SLA + architects | LTS branches |
Tell us a bit about your team and requirements. We’ll follow up with a tailored plan.