Skip to content
Meet the working Prodigi AION pilotExplore what’s available
Prodigi
Menu
HOW IT WORKS

From connection to confidence.

Start with selected metadata. Build a decision boundary. Keep the outcome explainable.

01

Connect a source

Create a source key in your private workspace. Your application or the supplied Python connector sends selected observations over HTTPS. Keys can be rotated or revoked.

02

Organize the context

Register systems, owners and authority profiles. Link risks, controls and evidence to the work they support.

03

Evaluate a proposed action

An integrated application submits a request. Policies evaluate it as allow, deny or review. A request with no matching policy is routed for review.

04

Bring in a person when needed

The workspace owner reviews the request. Separate decision reviews record rationale, conditions, residual risk and expiration dates.

05

Execute within your application

Your application consumes an approved permit once, then performs its authorized action. Prodigi does not execute the action or shut down a remote system.

06

Report what is known

Review the recorded activity and decisions. Produce an executive brief from the saved systems, risks, evidence, assessments and delivery actions.

FOR YOUR TECHNICAL TEAM

An explicit integration boundary.

Send only the metadata you need. Keep credentials server-side. Test with fictional or non-sensitive records first.

Application → HTTPS API → Authentication → Validation → Encrypted storage
Proposed action → Policy → Owner review when required → Single-use permit
Open integration guide Explore connections
YOUR NEXT STEP

Make the next action
an accountable one.