Describe what should flow where. Nova assembles the rest.
NovaNOVA — KEPLER'S BUILD SPECIALIST
Describe what should flow where. Nova assembles the rest.
When a request becomes a build, Kepler launches Nova to assemble the required Orbit artifacts stage by stage on a live rail, with explicit confirmation before activation or any other risky action.
Whole integrations · Live build rail · Gated activation
One stage for a message type, eight for a whole integration. Never padded.
Partners, connections, message types, MAPR AI mappings, process flows.
Activation and anything irreversible waits for your explicit confirmation.
Watch the integration assemble itself.
Nova is the build-focused expression of Kepler: same engine, sharper focus.
- 01You ask Kepler to build
“Set up the inbound 850 flow from ACME: partner, SFTP pickup, message type, mapping, flow.”
- 02Kepler launches Nova
You watch the handoff live. Nova comes online and the build rail rises with exactly the stages this task needs.
- 03Nova hands the build back
Stage by stage to done, confirmation gates on the risky parts, every artifact deep-linked for inspection.
Whole integrations, not fragments
Nova does not hand your team code to deploy. It creates the native Orbit objects the team will operate.
Whole integrations, not fragments
Trading partners, connections, message types, MAPR AI mappings, lookup tables, and process flows, wired together with the same naming conventions and required fields the UI enforces.
A rail sized to the task
Only the stages your request needs. A single message type is two stages; a full integration might be eight. Declined work is marked skipped, never silently dropped.
Grounded in your tenant
Nova resolves names against your real data before creating anything. Existing partners are reused, duplicates flagged, and identifiers verified rather than guessed.
Same engine as Kepler
Nova is Kepler in build focus. Ask a question mid-build and Kepler answers; the rail keeps its state. One continuous experience, not a second bot.
ONE ENGINE · ONE EXPERIENCE
It starts with Kepler. It always comes back to Kepler.
Nova is never a disconnected model or a separate bot. Ask Kepler a question mid-build and it answers; the rail keeps its state. When the build ends, everything is completed, skipped, or waiting on you.
Meet Kepler
Fast to build. Impossible to run away.
Confirmation gates
Flow activation, production runs, deletes, and outward-facing sends pause the rail until you explicitly confirm. Nova cannot approve itself; authority comes from your reply.
Your permissions, exactly
Every stage runs under your own access, re-checked per action. Nova can never create or activate anything you could not yourself.
Inspectable output
Every artifact Nova creates comes back as a deep link. Open the mapping, the connection, the flow, and review before anything goes live.
Bring an integration brief. Watch Nova assemble it.
Your partner spec and two sample payloads are enough for a 30-minute engineer-led session in a live sandbox.
Real brief, real samplesLive build railNothing activates without you