Product BriefACTIVE
Iskra
Problem: Turn work goals and context into repeatable workflows with explicit action authority and operator oversight.
Self-hosted working cognition and bounded workflow execution with operator oversight.
Best Fit
- Repeatable Operator-Controlled AI Workflows: Operations managers, analysts, and content teams seeking reproducible workflow templates with mandatory operator verification gates.
What exists today
- Persisted pipeline and queue-backed workflow execution
- Working-knowledge and file retrieval within supported flows
- Operator/admin/triage and audit surfaces
- External delivery and publishing through configured connectors (within bounds)
- Provider-specific AI execution; full provider sovereignty is not yet materialized (within bounds)
- Customer self-hosting within documented environment constraints (within bounds)
Explicitly not included
- 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
Evidence (Proof)
Claim Verification
VERIFIED
Operational Proof
PENDING_EVIDENCE
Operational evidence has not yet been recorded in the proof layer.
Last reviewed: 2026-09-28
Deployment Modes
- Operator-assisted pilot
Related Technical Reading
Commercial Entry
Status: AVAILABLE_BOUNDED
What to send us:
Request Iskra pilot →- Primary business or technical problem
- Current workflow and operator roles
- Data sensitivity and residency policies
- Preferred deployment environment (Self-hosted VM / Docker / On-Prem)
- Model strategy preference (local open-weight vs external API)