Why Orqista?
The name, the metaphor, and the ecosystem behind the platform.
The name, the metaphor, and the ecosystem behind the platform.
Orqista comes from orquesta — Spanish for orchestra.
An orchestra is the perfect metaphor: many specialized musicians, each expert in their instrument, performing together under a conductor.
The q in Orqista is highlighted in amber — the conductor's golden color.
The golden node. Represents you — the human who directs the orchestra.
Blue nodes in a semicircle. Each is an expert agent.
Lines from conductor to musicians. The flow of control.
Every subsystem in Orqista has an Orqi identity — a named capability within the platform.
Knowledge query hub — agents draw from curated notebooks, project conventions, and domain expertise across all connected sources.
Three-layer guardrail engine — global, project, and task-specific constraints that ensure agents never exceed their boundaries.
Open adapter architecture — pluggable integrations for code hosting, project tracking, documentation, and team communication.
Project DNA scanner — auto-detects conventions, patterns, dependencies, and architecture from any repository.
Developer sandbox — Prompt Lab, Guardrail Tester, and Dry Run for safe experimentation before production use.
Command-line interface — full programmatic control via the @orqista/cli package and shared typed API client.
These are some of the core systems — every capability in the platform gets an Orqi identity, and the ecosystem continues to grow.
Deep Space
#0D1117
Electric Cyan
#0EA5E9
Warm Amber
#F59E0B
Surface
#161B22