# Opheleon Full Context

## What Opheleon Does

Opheleon helps teams plan complex software work without losing the reasoning behind what gets built. It turns business goals into implementation-ready plans by keeping the planning chain connected from business intent to product behavior to system design to execution.

The product is built around four connected planning layers:

- BRD: Business Requirements Document, covering the business goal, problem, scope, constraints, and success criteria.
- PRD: Product Requirements Document, covering product behavior, user flows, requirements, edge cases, and acceptance criteria.
- HLD: High-Level Design, covering system architecture, component responsibilities, data flow, and major technical decisions.
- LLD: Low-Level Design, covering implementation details such as APIs, data models, migrations, service changes, and task-ready work.

## Core Workflows

Teams can start from a plain-language goal when planning new work. Opheleon drafts the planning layers in order, with review points so the team can approve, edit, or revise the plan as it develops.

Teams can also connect GitHub and import an existing codebase. Import is primarily for initializing Opheleon from resources that already exist. Re-import is a recovery or documentation refresh workflow for committed docs that are materially stale, incomplete, or wrong; it is not required for most normal code changes.

When GitHub is connected, Opheleon can use code-change summaries as future planning context. This helps new BRDs, PRDs, HLDs, and LLDs account for recent implementation work. Change summaries are planning context, not automatically committed documentation. Human review is still required before generated plans become final.

## Document Types

BRDs answer why the work matters and what business outcome should be achieved.

PRDs answer what the product should do, who it is for, what edge cases matter, and what acceptance criteria should be met.

HLDs answer how the system should be shaped at an architectural level, including major components, responsibilities, data flow, and technical decisions.

LLDs answer how the work should be implemented in concrete, task-ready terms.

## Integrations

Opheleon integrates with GitHub for repository context, import, recovery re-import, and code-aware planning updates.

Opheleon can send implementation work to Linear or Trello so approved implementation plans can become executable tasks.

Additional product, billing, customer communication, and AI/model infrastructure integrations may support the service. Public docs should avoid internal implementation details and should focus on customer-visible workflows.

## Security And Data Posture

Opheleon stores customer workflow content to provide planning, history, continuity, and recovery. This may include project metadata, goals, tasks, generated planning documents, repository-derived context, comments, and related outputs.

The public Trust Center summarizes security practices at a buyer-friendly level. Public positioning should use high-level categories such as cloud-hosted infrastructure, encryption at rest and in transit, private production data stores, scoped identity and access controls, account-level authorization, secure integration handling, logging and monitoring, human-reviewed AI workflows, and vendor review available on request.

Generated planning documents and implementation outputs are drafts until reviewed and approved by the customer team. Security or compliance claims should not overstate certifications or customer-specific commitments unless they are documented separately.

## Current Beta Status

Opheleon is in closed beta. Prospective customers can apply for beta access from the homepage.

Beta pricing is $400/month per team. It includes 400 AI credits each month for planning runs and codebase imports. Additional usage is billed at $1 per credit. Pricing is available for the first 10 beta teams. Customers can cancel anytime.

## Canonical Links

- Homepage: https://opheleon.ai/
- Docs: https://opheleon.ai/docs/
- Trust Center: https://opheleon.ai/trust-center
- Terms: https://opheleon.ai/terms
- Privacy: https://opheleon.ai/privacy
- Quickstart: https://opheleon.ai/docs/start-here/quickstart
- Who Should Use Opheleon: https://opheleon.ai/docs/start-here/who-should-use-opheleon
- Choosing a Workflow: https://opheleon.ai/docs/start-here/choosing-a-workflow
- Planning Pipeline: https://opheleon.ai/docs/features/planning-pipeline
- Codebase Import: https://opheleon.ai/docs/features/codebase-import
- Re-Import: https://opheleon.ai/docs/features/re-import
- Human Review Gates: https://opheleon.ai/docs/features/human-review-gates
- AI Reviewer: https://opheleon.ai/docs/features/ai-reviewer
- Fast Path Mode: https://opheleon.ai/docs/features/fast-path-mode
- Integrations: https://opheleon.ai/docs/features/integrations
- Security & Data: https://opheleon.ai/docs/reference/security-and-data
- FAQ: https://opheleon.ai/docs/reference/faq
- Sample Project: https://opheleon.ai/docs/examples/sample-project