Skip to main content
ORCA is organized around five building blocks. You set them up roughly in this order, and everything downstream depends on the ones before it.

1. Account & tenancy

Your organization’s isolated space, its users, and their roles.

2. The AI engine

The Anthropic API key and model routing that power the agent.

3. Oracle connections

One Oracle Fusion pod, its credentials, and its discovered metadata.

4. The workspace

Projects, cycles, and entities — where a conversion runs.

5. The agent & chat

The autonomous conversion agent and ask-anything chat.

​
The conversion lifecycle

A real conversion isn’t one load — it’s a series of cycles that get faster and cleaner as they move toward go-live. You start with a POC on a test pod (cycle-0), work the errors until it’s clean, then promote cycle by cycle toward the production cutover — each one faster because ORCA carries your mappings and learnings forward.

See the conversion lifecycle in detail

The full cycle-by-cycle flow, how promotion works, and why each cycle is faster than the last.