Use cases
What MuleSoft builders do with Cockpit in five days.
Beta · $50 first Project. API-led layers, Salesforce sync stubs, isolated desktops for banking, government, and enterprise programs, and the IDE panels that keep you on the thread.
Use cases
API-led connectivity, in one IDE
Use Ask to read what is already in the Anypoint org, Plan to sequence a new API-led layer, and Agent mode to scaffold the Mule project on a dedicated Linux Project. Connections, the bot, and the VM stay on screen so you are never guessing which layer you are editing.
Salesforce sync without the tab pile
Save Salesforce and Anypoint credentials on the website vault. Desktop Cockpit hydrates them after Sign in. When a Connected App needs a browser handshake, hand the VM the session instead of pasting secrets into Slack or a laptop browser. Built for generic enterprise CRM sync — not a named agency project.
Banking, government, and enterprise benches
Keep client Anypoint work off a personal laptop image. Consultants on banking, government, and enterprise programs get a short-lived Linux Project, sign in with their own Connected App, and leave less residue when the engagement ends. We do not name specific agencies on this site.
Postman and GitHub in the loop
Optional vault keys cover Postman and GitHub. Hydrate them into the desktop after Sign in, then ask the bot to open a collection, clone a Mule repo, or keep the Project aligned with the remote. The IDE panels show connection state so you know what the bot can actually reach.
A dedicated VM for OAuth handoff
OAuth and Connected App consent often need a real browser. Cockpit’s model is 1:1: each Project owns one cloud VM. Use the right-hand VM panel when a flow needs a human to click Allow, then return to Ask / Plan / Agent mode without losing the thread.
Ask, Plan, Agent — create to deploy
Same chat, different permission to move. Ask reads CloudHub, Runtime Fabric, and the APIs nobody is policing. Plan turns a ticket into a sequence. Agent carries work through the project. Deploy prompts are Beta — they depend on what your Anypoint Connected App can already do.
Standardize team onboarding
Point a teammate at orcaesb.com to request access. After their Clerk invite, they set a password, fill the vault, download Cockpit, and Sign in. They land in Ask. The website creates their first Project on first account visit. Less time rebuilding JDKs; more time reading the tenant they just inherited.
A ready MuleSoft + Cursor Project
Spin up a dedicated cloud Project instead of spending a weekend on JDKs, Studio plugins, and conflicting local tools. You bring Cursor and Anypoint credentials; we provide the machine and Orca Cockpit. The first Project is created on first account visit — the website never stores AWS keys, and provisioning is a webhook to our infra.
Works with
Built for the tools you already have. Logos identify products Orca Cockpit connects to — not a partnership or endorsement.
- Salesforce
- MuleSoft
- Cursor
- Anypoint
How to use it
Same path for every Project.
Accept your Clerk invite, set a password, fill the vault on the website, download Cockpit, Sign in, land in Ask. Your first Project is created on first account visit.
- 01
Accept your invite
Request access on orcaesb.com — not in the IDE. We review each request and send a Clerk invite. Set a password on app.orcaesb.com, then land on Setup to import vault YAML and queue your default t3.large Project.
- 02
Fill the vault
Save Cursor, Anypoint, and optional Salesforce, GitHub, and Postman secrets on the website only.
- 03
Download and Sign in
Install Orca Cockpit for Mac or Windows, then choose Sign in. Same Clerk account. You land in Ask.
- 04
Use your default Project
A Project is a dedicated Linux VM plus its filesystem. The first one is created on first account visit as t3.large (2 vCPU · 8 GiB). Chat in Orca Cockpit IDE drives create → code → deploy.
Request access for a real Mule week.
Access is invite-only. Email sivaji@orcaesb.com or rajiv@orcaesb.com — we review each request and send a Clerk invite one user at a time. After you set a password, fill the vault, download Cockpit, and Sign in from the desktop to land in Ask. Your first Project is created on first Setup visit. No checkout during this beta.