Orbit Pro connects Django runtime evidence, the proposed code change and the next execution. Move from ticket to fix with proof — without sending your telemetry to another platform.
Founder target: $12/month · Open-source core on PyPI · no hosted telemetry
A coding agent can produce a plausible patch and passing unit tests while the original runtime failure, slow query or side effect remains unresolved.
Orbit Pro connects the original evidence, the investigation, the commit and the next execution so the developer can see what improved, what regressed and what still needs attention.
Connect the request, exception, SQL, logs, jobs and AI calls that produced the symptom.
Turn the ticket or error into a local investigation with hypotheses and test targets.
Give Codex, Claude Code or Cursor bounded runtime context instead of a vague prompt.
Keep the patch, regression tests and release decision tied to observed behavior.
Compare the next runtime window and show what improved, regressed or remains unknown.
Save a local baseline, compare the release candidate and produce a pass, warning or blocker with supporting evidence.
Keep the symptom, evidence, hypotheses, test plan, fix and verification result together inside your project.
Orbit provides local MCP context and bundles. You keep using Codex, Claude Code, Cursor or another compatible agent.
Link the candidate change to a new runtime window and verify whether the original signal disappeared without new regressions.
Trace models, tokens, latency, errors, tool names and agent loops without collecting prompts or tool arguments by default.
Audit masking, agent-visible fields, capture limits and environment policy before runtime evidence reaches a coding tool.
Install Django Orbit today. Its dashboard, watchers, MCP tools, incident bundles and safety controls remain MIT-licensed. Pro will add the repeatable verification workflow on top.
# available today
pip install django-orbit
# optional agent tools
pip install "django-orbit[mcp]"
# Orbit Pro founder workflow — self-hosted
baseline → agent fix → runtime verification
The Orbit you know. MIT-licensed, no strings.
Target founder price. Or $120/year. Final scope and launch follow waitlist validation.
Optional hands-on help. The software subscription never requires a service package.
Pro reads the Orbit storage already running with your Django project. There is no hosted ingestion endpoint.
Prompts, completions and tool arguments remain excluded by default. Agent-facing evidence stays bounded and auditable.
Preview exactly what an agent will receive before an investigation or verification bundle is shared.
License checks and Pro analysis stay outside request handling. A Pro failure cannot take down the host application.
We are validating the first self-hosted Orbit Pro release for Django. Tell us which workflow is worth paying for before we lock the first release.
No payment today. No hosted telemetry. Founder feedback determines the first paid release.
No. Django Orbit stays MIT-licensed with every current feature intact. Pro is a separate self-hosted extension for repeatable release and verification workflows.
The founder target is Release Guard, saved investigations, agent verification, production safety profiles and ongoing Pro updates. Local capture, dashboard, MCP and incident bundles remain free.
In the Orbit storage configured for your own Django application. Orbit Pro does not require a hosted ingestion service or a remote telemetry database.
Pro analysis and license checks stay outside the request path. Orbit's fail-silent watcher design remains the host-app safety boundary.
Yes. Compatibility updates, security fixes and regular Pro improvements are included while subscribed. Setup reviews, priority support and custom integrations are optional services.
No. You bring Codex, Claude Code, Cursor or another coding agent. Orbit provides the local evidence and verification workflow, so there is no bundled inference cost.
Django is the first product and receives the deepest support. The long-term evidence contract can support FastAPI and other frameworks after the Django verification workflow is proven.