Developers

Built like infrastructure.

One call between intent and execution. The SDK and APIs below describe the intended developer model and are available through the Developer Preview.

Philosophy

Integration principles.

Integrate, don't replace

Pomerion wraps the point where intent becomes command. Your planner, perception and controllers stay yours.

Fail closed

If a decision cannot be made, the action does not happen.

Policy as code

Policies are versioned, reviewed and deployed like any other critical software.

Explainable decisions

Every decision carries the identity, model, policy and context that produced it.

API concepts

Six nouns.

machine

A physical system with a verifiable identity.

model

A versioned piece of intelligence permitted to control machines.

action

A named physical capability, e.g. enter_zone, grasp, takeoff.

resource

What the action targets: a zone, an object, an airspace.

policy

Declarative rules binding the above under conditions.

decision

allow or deny, with reasons, recorded to audit.

decision.json

1{
2  "decision": "deny",
3  "machine": "amr-042",
4  "model": "navigation-v18",
5  "action": "enter_restricted_zone",
6  "policy": "restricted_zone@v3",
7  "reason": "zone.classification == \"restricted\"",
8  "audit_id": "dec_8f21…"
9}

SDK structure

Where it lives in your stack.

TypeScript@pomerion/sdk
Pythonpomerion
C++libpomerion
Rustpomerion-rs
ROS 2pomerion_ros
Planned SDK surface. Availability varies during preview.

nav_guard.py

1from pomerion import Client
2
3pom = Client.from_device()
4
5def on_goal(goal):
6    d = pom.authorize(
7        action="enter_zone",
8        resource=goal.zone,
9    )
10    if not d.allowed:
11        return reject(goal, d.reason)
12    controller.execute(goal)

Build with the Developer Preview.

Apply for access