OPEN-SOURCE CORE
Software you can inspect, run, and question.
Orkestr keeps the generic runtime, interface, tests, and documentation public. Private deployments keep real credentials, customer configuration, and operational records outside the repository.
A SIMPLE TECHNICAL VIEW
The agent does the work. Orkestr keeps it visible and controlled.
Tasks live in named threads. The configured agent works in its assigned workspace. Orkestr tracks status, approvals, resources, and delivery. Approved connectors or managed browsers reach external tools.
- 01Request
A person or approved trigger starts a task.
- 02Agent
The configured runtime works inside its assigned workspace and permissions.
- 03Control
Orkestr records status, warnings, approvals, and history.
- 04Connection
An approved connector or managed browser performs the allowed action.
PUBLIC-ALPHA QUICK START
Run the core locally.
Use illustrative data. Keep private configuration, secrets, and live sessions outside the repository.
git clone https://github.com/otcan/orkestr.git
cd orkestr
npm ci
npm run build
npm run demo:coding-agentPUBLIC AND PRIVATE
Know what belongs where.
- Public
- Generic runtime, interface, connector contracts, deployment scaffolding, tests, and illustrative examples.
- Private
- Customer configuration, credentials, infrastructure, specialized adapters, and operational evidence.
- Managed work
- Process design, implementation, hardening, release, monitoring, and support within the agreed boundary.
PUBLIC-ALPHA REALITY
Build with the current limits in view.
- Interfaces and configuration can change.
- Not every connection is available or production-ready in every deployment.
- Self-hosting transfers security, retention, recovery, and operations to the environment owner.
- Managed implementation does not turn the open-source core into unrestricted hosted software.