What it solves
Turn work goals and context into repeatable workflows with explicit action authority and operator oversight.
Iskra · Materialized self-hosted workflow platform; bounded customer delivery
Iskra
Self-hosted working cognition and bounded workflow execution with operator oversight.
Who it is for
Teams needing repeatable work execution, working-knowledge retrieval and operator oversight; content is one supported use case.
What works now
- Persisted pipeline and queue-backed workflow execution
- Working-knowledge and file retrieval within supported flows
- Operator/admin/triage and audit surfaces
Boundaries
- External delivery and publishing through configured connectors
- Provider-specific AI execution; full provider sovereignty is not yet materialized
- Customer self-hosting within documented environment constraints
- Not an unrestricted autonomous workflow executor
- Common Local Governor enforcement is not yet universal for external side effects
- No verified independent customer cold-recovery or universal public SLA
- Fully autonomous self-serve SaaS
- Broad unassisted public access
- Automated execution guarantees without operator intervention
Delivery
- Operator-assisted pilot
Technical evidence
Proof & Evidence Status
Claim Snapshot: Verified (VERIFIED)
Product claim source snapshot in Iskra repository reviewed. (Reviewed: 2026-09-28)
Runtime / Operational Proof: Pending Evidence (PENDING_EVIDENCE)
Operational evidence has not yet been recorded in the proof layer.
Explicit Operational Boundaries:
- External delivery limited to operator-assisted pilot
- Public self-serve blocked
- Expansion on hold pending readiness reviews
Evidence is snapshot-scoped. Claim verification does not imply universal production readiness, certification, or SLA guarantees.
Read Proof Methodology & Evidence Model →