Buy the repository, or have it built around you.
Two paths. Both let you build in source you control.
Options OS
The spec-driven framework and private source repository for building an owned crypto-options engine.
- 21 reusable Python libraries with matching specifications
- Pricing, surface, portfolio, cost, hedging, messaging, and runtime foundations
- Adapter contracts and Deribit reference implementation
- Engine scaffold and composition path
- Claude Code and Codex build workflows
- Verification and deployment tooling
- Source you can inspect, extend, and operate
Implementation services
Engineering ownership for the strategy, composition, and operating layer that remains specific to your engine.
- Trading-system definition and PnL-mechanism specification
- Framework and venue composition
- Engine architecture and implementation
- Strategy, mandate, risk, and lifecycle policy
- Runtime, recovery, and deployment architecture
- Verification and conformance evidence
- Source delivered in your controlled repository
Access in four steps.
Enter the GitHub username that should receive access.
Complete the one-time purchase.
Receive and accept the private repository invitation.
Follow the included quick start from engine definition to verified implementation.
Asked before buying.
Is Options OS a trading bot?
No. It is a spec-driven engineering framework for building an owned options engine.
Does it include a profitable trading strategy?
No. Strategy logic and the PnL mechanism remain specific to the engine you build.
What is already implemented?
Reusable options-system libraries and their specifications, runtime and messaging contracts, adapter contracts, the Deribit reference adapter, the trading-system definition and specification framework, coding-agent workflows, deployment foundations, and verification tooling.
What do I do after cloning the repository?
Follow the included quick start, complete the trading-system definition, review the generated engineering specification, compose the required framework components, and build with Claude Code or Codex against the supplied contracts.
What remains mine to build?
Your alpha and PnL mechanism, entry and exit logic, runtime cycle, book model, risk and lifecycle policy, accounts, credentials, deployment, monitoring, workload validation, and live-operation approval remain yours.
Is the complete repository private?
Yes. Buyers receive access through a private GitHub invitation after payment.
Is it ready to trade live immediately?
No. Credentials, configuration, validation, deployment, monitoring, and live approval remain the builder’s responsibility.
What technical knowledge is required?
The product is built for people comfortable with Python, Git, software architecture, and options-system concepts.
What if I need LeanOS to implement the system?
Choose a custom build when you want LeanOS to take the engine from trading-system definition through architecture, implementation, verification, and deployment design.
Purchase, repository access, or product questions: bella@leanos.tech