Pay for Governance. Keep AI Provider Costs Direct.

A user is anyone who can log into your Pristan environment to use or administer approved agents. This includes employees, contractors, or any team member with an active account. API-only integrations do not count as individual users unless those people also have Pristan accounts.

Deployment changes are planned with the Pristan team because infrastructure, secrets, provider connections, stored content, and policy requirements can differ between environments. We will scope the migration path and validation steps with you.

Yes. The self-service evaluation provides a private workspace for one Super Admin and up to ten users for seven days. Guided evaluations can be scoped separately for more complex requirements.

Onboarding, support channels, service hours, response targets, and any professional services are defined in your commercial agreement so they match the deployment and operating model.

Pristan supports compliance workflows with agent inventory, owner records, access policy, DLP evidence, retention settings, audit logging, and role-based access control. Data boundaries depend on the selected deployment and configured providers: customer-managed deployments keep the Pristan application and storage in the customer environment, while requests to external AI or connector services follow the routes and credentials the customer enables.

Start by cataloging the agents, providers, owners, and data sources you use today. We can then scope which configuration, metadata, files, or conversation records can be transferred, which items need to be recreated, and how both systems should operate during the transition.

Requirements depend on users, concurrency, model routing, file volume, retention, integrations, and availability targets. Pristan supports a Docker-based deployment with PostgreSQL, Redis, and S3-compatible object storage; we size and validate the production topology with your infrastructure team.