> ## Documentation Index
> Fetch the complete documentation index at: https://docs.prets.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Next Steps

> How compliance is built into the integration flow

## Compliance, built into the flow

Prets does not rely on policy documents to stay compliant.

Compliance is enforced through design:

* customers make all choices themselves;
* no option is preselected;
* no advice or suitability logic is applied;
* decisions stay with providers;
* every step is traceable.

This keeps your organisation outside regulated activities by construction.

## What comes next

When you move forward, documentation covers:

* security and authentication;
* API and webhook reference;
* test and production environments;
* onboarding and rollout support.

Most teams start with an embed. Integration deepens as volume grows.

<CardGroup cols={2}>
  <Card title="API Reference" icon="terminal" href="/api-reference">
    Technical API documentation for integration endpoints.
  </Card>

  <Card title="Book a Demo" icon="calendar" href="https://www.prets.io/get-in-touch">
    See how Prets fits into your setup.
  </Card>
</CardGroup>