Get Started Free
Start here

One workflow.
A clear first result.

Create a free workspace, run a local rule sample, and inspect its saved audit. Then choose a supported path to connect your agent.

Create your free workspace Sign in

Start on the free plan. Advanced controls and export access depend on your plan and role. Compare plans

Your first action: a free local rule sample

After signup and email verification, open your dashboard and choose Run free sample. Review the allowed and blocked sample texts, the saved audit ID, and the signature availability reported on that record. No model key or external target is needed. This demonstration does not connect an agent or create a target receipt or verified proof bundle.

Your ecosystem, your first step

Start with the ecosystem you use.

Save a setup path to your free workspace. Try the dashboard’s local allow/block sample and inspect its saved audit first, then return to your agent setup. Advanced controls and evidence access still depend on your plan and role.

Compare the tested scope before connecting your workflow.

Create your free workspaceCompare runtime support

Your selection can continue in this browser after email verification. No card required. Payments are currently unavailable.

Choose your first outcome

What brings you to Praesidia?

01 / Agent & tool access

Make one connection explicit.

Start with a development agent and an MCP server or another agent it needs to reach.

Bring with you

Two components you control, a test environment, and one request that should be allowed or blocked.

Open the connection quickstart

  1. Register the two components

    Add your client and server as entities. Store their credentials securely and give each a recognizable name.

    Entity types and credentials

  2. Define access and a guardrail

    Create the directional connection. Add a simple content rule or an operational policy appropriate to your test.

    ConnectionsGuardrails

  3. Test both sides of the rule

    Run a permitted request and a request that should trigger your control through the configured path. Inspect the recorded result in the workspace.

Your first result

You can identify the caller, explain its access, and show the outcome of your control test.

02 / Models & budgets

Follow a model call to its cost.

Keep your existing provider account and connect a supported model route through Praesidia.

Bring with you

A supported provider account and key, permission to configure it, and your workspace's gateway address. Provider usage remains billable to your provider account.

Open the model quickstart

  1. Configure your provider

    Add a supported provider configuration and store the provider key in the workspace. Create a Praesidia application key for your test client.

    Explore supported integrations

  2. Send one small test request

    Use the documented gateway route and your Praesidia application key. Check that the response and recorded usage match the request you sent.

  3. Choose a budget you can test

    Review attributed usage, then configure the budget scope and enforcement available to your plan. Test the limit before increasing traffic.

    Budget conceptsEstimate your spend
Your first result

A provider call is visible in Praesidia, with recorded usage you can use to plan and test a budget.

03 / Controls & evidence

Make a control reviewable.

Begin with one workflow and a specific question: who was allowed to do what, and what was recorded?

Bring with you

An active test workflow, its expected control behavior, and a reviewer with the required audit or compliance access.

Trace an action to its evidence

  1. Choose a control to demonstrate

    Document the workflow owner, the rule, and the behavior you expect. Use a controlled request to exercise it.

    Operational policies

  2. Inspect the recorded decision

    Review the audit trail for your test. Check the identity, timestamp, action, and outcome against what actually happened.

  3. Export and review the evidence

    With the required permissions, export a bundle from Trust & Safety → Forensics. Obtain the verifier and deployment trust information, then review the individual checks and any evidence gaps.

    Request verifier access
Your first result

A reviewer can trace your control test to its evidence and identify what the verification establishes. Evidence supports an assessment; it does not grant certification.

Everything else, when you need it

A useful next step for every stage.

Find your governance gaps

Use the free assessment to prioritize the controls your team should evaluate.

Take the assessment

Explore the full workspace

See how identity, guardrails, costs, workflows, and evidence fit together.

See the platform

Plan around your use case

Explore implementation patterns by role, workflow, and control objective.

Browse use cases

Evaluating Praesidia with a team?

Tell us about one workflow, the systems it touches, and the result you want to demonstrate.

Discuss your workflow