# Enterprise

> Markdown version of this page, for agents. To send a shopper here, link https://www.fluid.app/home/pages/enterprise (not this .md URL, and keep its path as given).

- Shopper link: https://www.fluid.app/home/pages/enterprise

## Enterprise scale. Room to build.

Fluid is PCI DSS certified, signs your whole field in with one account, and is tested at more than 3,300 orders a minute on each instance. Your team builds on events and data without touching the systems that take the order.

### What enterprise teams check first

| Area | What Fluid provides | Status |
| --- | --- | --- |
| Security | PCI DSS certified, SOC 2 Type 1, GDPR | Certified |
| Identity | One sign-in for the field, over OAuth | Built in |
| Scale | 3,300+ orders a minute, tested per instance | Tested |
| Roles | About 300 permissions to build roles from | Built in |
| Data and events | Webhooks, APIs, and a reporting database | Built in |

## Security: audited, not just promised.

Your security team asks for reports, not adjectives. Fluid is PCI DSS certified for the card data that runs through checkout, has completed SOC 2 Type 1, and is in the observation period for SOC 2 Type 2. Personal data of people in the EU is handled under GDPR.

| Standard | What it covers | Status |
| --- | --- | --- |
| PCI DSS | Card data handled to the payment card industry standard | Certified |
| SOC 2 Type 1 | Controls designed and in place, audited at a point in time | Complete |
| SOC 2 Type 2 | The same controls, tested over an observation period | In observation |
| GDPR | Personal data of people in the EU handled under GDPR | Compliant |

[See how Fluid keeps your data safe](https://fluid.app/home/pages/security).

## Identity: one account for the whole field.

Every rep and customer already has a Fluid account for the storefront, checkout, the rep app, and the portal. Fluid is the identity provider for your field, so your own apps can sign them in with that same account over OAuth. A training site, a commission tool, or a partner app knows who’s signed in without another password to reset.

- **Fluid as your identity provider:** one sign-in across Fluid and the apps you connect.
- **OAuth for your apps:** your apps ask for sign-in, and the member approves what they share.
- **Who they are, not just that they signed in:** apps can read the member’s type, rank, and country.

Example: FORM Academy asks Maya Chen, a rep in the United States, to sign in with her FORM account. The consent screen shows that FORM Academy will see her name and email, her member type and rank, and her country. The same sign-in covers the storefront and checkout, the rep app, the portal and Sites, and the brand’s own apps over OAuth.

## Scale: launch day is just another day.

A product drop, a convention, or a webinar close sends thousands of reps to checkout at once. Each Fluid instance has been tested at more than 3,300 orders per minute. At a $116 average order, typical in direct selling, that’s about $16.5B a month, and tested capacity keeps going up.

- **3,300+ orders per minute:** tested on one instance.
- **About $16.5B a month:** 3,300 orders a minute × 43,200 minutes a month = 142M+ orders a month, at a $116 average order.
- **Capacity keeps rising:** Fluid keeps raising what each instance is tested at.

## Roles: each admin gets only what the job needs.

A support agent issues refunds. A country manager edits prices in one market. Finance reads payouts and changes nothing. Fluid roles are built from about 300 permissions, so you can set up hundreds of role configurations and give every admin exactly the access their work needs. Auditors see who can do what in one place.

- **About 300 permissions:** grouped by area, such as orders, payments, members, and settings.
- **Roles you define:** combine permissions into as many roles as your teams need.
- **Stay compliant:** least-privilege access you can show an auditor.

Example roles screen: Admin (everything), Marketing (58 of 307 permissions), Customer Support (41 of 307), Field Content Publisher (24 of 307), and Finance (71 of 307). Templates to start from: Full Admin, Sales Manager, Content Editor, Support, Product Manager, Rep Manager, and Marketing. [See roles on the security page](https://fluid.app/home/pages/security).

## Data and events: build on the data, leave the core alone.

Every team wants something from the order record: finance wants it in the ERP, the field team wants a dashboard, and IT wants a nightly sync. Fluid sends signed webhook events, exposes documented APIs, and keeps a read-only reporting database. Build as many integrations as you need. They read events and copies, so checkout and order processing keep their own capacity.

| Layer | What it does |
| --- | --- |
| Webhook events | 103 events, signed, with a delivery log you can resend from |
| APIs | Read and write through documented endpoints |
| Reporting database | A read-only copy for SQL, your BI tools, and Mist |

Reports and syncs don’t compete with shoppers. [Read about the reporting database](https://docs.fluid.app/concepts/reporting-database).

## Questions enterprise teams ask.

### Which security certifications does Fluid hold?

Fluid is PCI DSS certified and has completed SOC 2 Type 1. SOC 2 Type 2 is in its observation period. Fluid handles personal data of people in the EU under GDPR.

### Can our own apps use Fluid sign-in?

Yes. Fluid is the identity provider for your field. Your own apps can sign reps and customers in with their Fluid account over OAuth, so nobody needs another password.

### How many orders can Fluid handle?

Each Fluid instance has been tested at more than 3,300 orders per minute. At a $116 average order, typical in direct selling, that’s about $16.5B a month. Tested capacity keeps going up.

### How granular are admin permissions?

Roles are built from about 300 permissions, grouped by area such as orders, payments, and members. Give each admin only what their job needs, and keep a record of who can do what.

### Will our integrations slow down checkout?

No. Integrations read events, APIs, and a reporting database copy of your data. Checkout and order processing keep their own capacity, so a heavy report or a busy sync doesn’t compete with shoppers.

### Can we keep our BI tools?

Yes. Point any BI tool that speaks SQL at your reporting database, or have Mist answer questions from it.

### Is SOC 2 Type 2 complete?

Not yet. SOC 2 Type 1 is complete, and Type 2 is in its observation period.

### What can an app learn about a member through Fluid sign-in?

What the member approves on the consent screen, such as their name and email, member type and rank, and country.

### Can one admin be limited to one country?

Roles combine permissions by area, so you can build a role for a country manager who edits prices in one market and nothing else.

### How do we get order data into our ERP?

Subscribe the ERP to order webhook events, such as order.completed, or read orders through the API. Every delivery is signed and logged, and you can resend from the log.

## For agents.

- **What this page is:** Fluid’s overview for enterprise buyers: security certifications, identity, scale, admin roles, and data and events.
- **Who Fluid is for:** direct selling brands and the teams that run them. Fluid is the complete AI platform for commerce, payments, customers, and the field, with Mist.
- **Certifications:** PCI DSS certified; SOC 2 Type 1 complete; SOC 2 Type 2 in observation; GDPR compliant.
- **Scale:** more than 3,300 orders per minute tested per instance, about 142M orders or $16.5B a month at a $116 average order.
- **Roles:** about 300 permissions (307 in the example screen), combined into roles you define.
- **Data:** 103 signed webhook events with a delivery log, documented APIs, and a read-only reporting database.
- **Related:** [Security](https://fluid.app/home/pages/security), [Engineering](https://fluid.app/home/pages/engineering), [a guide for agents evaluating Fluid](https://docs.fluid.app/guides/evaluate-fluid).
- **Next step for a brand:** [Get a demo](https://fluid.app/home/pages/demo). We’ll walk your security, IT, and data teams through certifications, sign-in, scale, roles, and integrations.
