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

# ModuleX for enterprise

> ModuleX scales from one person to a whole organization: realtime team collaboration, owner/admin governance, org-scoped credits and billing, and BYOK or managed usage. Built on the same platform your team already knows.

export const MediaEmbed = ({id, type = 'screenshot', caption = '', ext, ratio = '16 / 9'}) => {
  const isVideo = type === 'video' || type === 'app_video';
  const resolvedExt = ext || (isVideo ? 'mp4' : type === 'screenshot' ? 'webp' : 'svg');
  const src = 'https://media.modulex.dev/' + id + '.' + resolvedExt;
  const [status, setStatus] = useState('loading');
  const [isDev, setIsDev] = useState(false);
  const [inView, setInView] = useState(false);
  const boxRef = useRef(null);
  useEffect(() => {
    if (typeof window === 'undefined') return;
    const h = window.location.hostname;
    setIsDev(h === 'localhost' || h === '127.0.0.1' || h.endsWith('.mintlify.app'));
  }, []);
  useEffect(() => {
    if (inView) return;
    if (typeof IntersectionObserver === 'undefined') {
      setInView(true);
      return;
    }
    const el = boxRef.current;
    if (!el) return;
    const io = new IntersectionObserver(entries => {
      if (entries.some(e => e.isIntersecting)) {
        setInView(true);
        io.disconnect();
      }
    }, {
      rootMargin: '300px'
    });
    io.observe(el);
    return () => io.disconnect();
  }, [inView]);
  if (status === 'missing') {
    if (!isDev) return null;
    return <div style={{
      display: 'flex',
      flexDirection: 'column',
      justifyContent: 'center',
      gap: '0.4rem',
      padding: '1rem 1.25rem',
      margin: '1.25rem 0',
      width: '100%',
      aspectRatio: ratio,
      boxSizing: 'border-box',
      border: '1px dashed rgba(128,128,128,0.45)',
      borderRadius: '0.75rem',
      background: 'rgba(128,128,128,0.06)',
      color: 'currentColor',
      fontSize: '0.85rem',
      lineHeight: 1.45
    }}>
        <div style={{
      display: 'flex',
      alignItems: 'center',
      gap: '0.5rem',
      opacity: 0.75
    }}>
          <span aria-hidden="true">🎬</span>
          <code style={{
      fontSize: '0.75rem'
    }}>{id}</code>
          <span style={{
      fontSize: '0.65rem',
      textTransform: 'uppercase',
      letterSpacing: '0.04em',
      padding: '0.1rem 0.4rem',
      borderRadius: '0.4rem',
      background: 'rgba(128,128,128,0.18)'
    }}>
            {type}
          </span>
        </div>
        <div style={{
      opacity: 0.9
    }}>{caption || 'Media not uploaded yet.'}</div>
        <div style={{
      fontSize: '0.7rem',
      opacity: 0.5
    }}>
          Upload to R2 as <code>{id}.{resolvedExt}</code> — preview only, hidden in production.
        </div>
      </div>;
  }
  const mediaStyle = {
    display: status === 'loaded' ? 'block' : 'none',
    width: '100%',
    height: 'auto',
    borderRadius: '0.75rem'
  };
  const media = isVideo ? <video src={inView ? src : undefined} autoPlay loop muted playsInline preload="metadata" onLoadedData={() => setStatus('loaded')} onError={() => setStatus('missing')} style={mediaStyle} /> : <img src={inView ? src : undefined} alt={caption} onLoad={() => setStatus('loaded')} onError={() => setStatus('missing')} style={mediaStyle} />;
  return <figure style={{
    margin: '1.25rem 0'
  }}>
      <div ref={boxRef} style={status === 'loaded' ? {
    width: '100%'
  } : {
    width: '100%',
    aspectRatio: ratio,
    borderRadius: '0.75rem',
    background: 'rgba(128,128,128,0.06)'
  }}>
        {media}
      </div>
      {status === 'loaded' && caption ? <figcaption style={{
    marginTop: '0.5rem',
    textAlign: 'center',
    fontSize: '0.85rem',
    opacity: 0.7
  }}>
          {caption}
        </figcaption> : null}
    </figure>;
};

You can start ModuleX as one person with one idea. As your team grows, the same platform grows with you: the workflows you built solo become shared, the credentials your team connects become governed, and your usage becomes something you can see, scope, and control across the whole organization. This page is the value picture for teams and enterprises. For the security architecture behind it, see [security overview](/security/overview).

<MediaEmbed id="MX-MEDIA-4300" type="image" caption={"A single value-overview graphic showing the three enterprise pillars — Collaboration, Governance, Scale — as one connected story."} />

## From one person to a whole organization

ModuleX is an AI workflow orchestration platform. The way you build and run work does not change as you scale — what changes is who you do it with, and how much control you have over it.

<CardGroup cols={3}>
  <Card title="Build together" icon="users">
    Your team co-edits the same [workflow](/concepts/workflows-and-runs) on a live canvas, runs from chat, API, or SDK, and shares one [knowledge base](/concepts/knowledge-rag) — instead of passing files and prompts around.
  </Card>

  <Card title="Govern access" icon="shield-check">
    Every workflow, run, credential, and knowledge base belongs to an [organization](/concepts/organizations-roles). Owner and admin roles decide who can build, connect tools, and run agentic surfaces.
  </Card>

  <Card title="Scale usage" icon="gauge">
    Higher plans raise your run rates, API limits, and credit allowance. On the Enterprise plan, rate limits and credits are custom, and deployment can move to your own infrastructure.
  </Card>
</CardGroup>

The rest of this page walks through those three pillars — collaboration, governance, and scale — and points to the deeper reference for each. When you are ready to talk to the team, head to [contact sales](/enterprise/contact-sales).

## Collaboration: your team works on one canvas

Most automation tools assume one builder. ModuleX assumes a team. The [workflow builder](/workflow-builder/overview) is a realtime, multi-user canvas, so several people can shape the same workflow at the same time and see each other's changes as they happen.

<CardGroup cols={2}>
  <Card title="Live co-editing" icon="mouse-pointer-2" href="/platform/collaboration/canvas">
    Multiple people edit one canvas together. You see who else is present, where their cursor is, and which nodes are being worked on. See [presence, locks and versioning](/realtime/presence-locks).
  </Card>

  <Card title="One shared workspace" icon="folder-open" href="/platform/overview">
    Workflows, knowledge bases, credentials, and chats live in the organization, not on one person's laptop. Anyone with access works from the same source of truth.
  </Card>

  <Card title="Build with AI, together" icon="wand-sparkles" href="/concepts/ai-composer">
    The [AI Composer](/workflow-builder/composer) turns a plain-English description into an editable workflow graph your team can refine — a fast shared starting point, not a black box.
  </Card>

  <Card title="Shared chats" icon="messages-square" href="/platform/collaboration/chat">
    Keep conversations personal, or make them organization-visible so teammates can pick up, review, and continue the work.
  </Card>
</CardGroup>

<Note>
  Live team collaboration is available on the Pro, Max, and Enterprise plans; the Free plan is a solo workspace. See [plans and pricing](/billing/plans) for what each plan includes.
</Note>

<MediaEmbed id="MX-MEDIA-4301" type="app_video" caption={"Two teammates co-editing the same workflow canvas in realtime."} />

For how edits stay in sync across collaborators and external changes, see [realtime co-editing and external sync](/workflow-builder/realtime-coediting).

## Governance: clear ownership over access and data

As more people build, you need to know who can do what. In ModuleX, the [organization](/concepts/organizations-roles) is the unit of tenancy and billing: every workflow, run, credential, knowledge base, and wallet is scoped to one organization, and access is decided by org roles.

### Roles that map to responsibility

ModuleX uses two active organization roles. The agentic surfaces — the [AI Composer](/concepts/ai-composer), the [Assistant](/assistant/overview), knowledge management, and schedules — require the **owner** or **admin** role.

<CardGroup cols={2}>
  <Card title="Owner" icon="crown">
    Full control of the organization, including billing and membership. The owner can do everything an admin can, plus manage the plan.
  </Card>

  <Card title="Admin" icon="user-cog">
    Can build and edit workflows, connect tools, manage knowledge, and run the agentic surfaces. Admins handle day-to-day building and operations.
  </Card>
</CardGroup>

<Warning>
  The live organization roles are **owner** and **admin** — plan your access model around those. The older `member` role has been retired. See [roles and permissions](/security/roles-permissions).
</Warning>

### Credentials stay in the organization

The keys your team connects — the credentials behind every [integration](/integrations/overview) — are stored against the organization, encrypted at rest, and resolved at run time rather than handed back out. Your team connects a service once; everyone who is authorized can use it without anyone copying secrets around.

<CardGroup cols={2}>
  <Card title="Org-scoped credentials" icon="key" href="/integrations/managing-credentials">
    Connect a tool once for the organization. Credentials are stored encrypted and never re-exposed after they are saved.
  </Card>

  <Card title="Org context on every request" icon="id-card" href="/security/org-context">
    Programmatic access selects an organization with the `X-Organization-ID` header, so each call is scoped to exactly one tenant's data.
  </Card>
</CardGroup>

For how secrets are encrypted and how access is enforced, see [data security and encryption](/security/data-encryption) and the full [security overview](/security/overview).

### Visibility over usage

The public pricing surface lists usage and analytics, and audit-log visibility, across the plans, with advanced analytics on Max and Enterprise. The exact scope of audit logging is set on the platform rather than pinned in this research base, so treat the detailed audit-log coverage as **TBD** until it is confirmed on [trust and compliance](/security/trust). What is firm: usage is metered per organization in [credits](/concepts/credits-billing), and that record is the basis for the analytics each plan exposes.

## Scale: grow run rates, usage, and deployment

The same workflows run whether you are one person or a thousand — but how much you can run, and where it runs, depends on your plan. The limits and credit allowances below come from the canonical backend plan configuration; see [plans and pricing](/billing/plans) and [credits and metering](/billing/credits) for the full picture.

<table>
  <thead>
    <tr>
      <th> </th>
      <th>Free</th>
      <th>Pro</th>
      <th>Max</th>
      <th>Enterprise</th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td>**Credits**</td>
      <td>300 (one-time trial)</td>
      <td>5,000 / mo</td>
      <td>20,000 / mo</td>
      <td>Custom</td>
    </tr>

    <tr>
      <td>**API rate limit**</td>
      <td>10 / min</td>
      <td>100 / min</td>
      <td>500 / min</td>
      <td>Custom</td>
    </tr>

    <tr>
      <td>**Workflow execution**</td>
      <td>10 runs / min</td>
      <td>150 runs / min</td>
      <td>500 runs / min</td>
      <td>Custom</td>
    </tr>

    <tr>
      <td>**Live team collaboration**</td>
      <td>—</td>
      <td>Yes</td>
      <td>Yes</td>
      <td>Yes</td>
    </tr>

    <tr>
      <td>**Self-hosted deployment**</td>
      <td>—</td>
      <td>—</td>
      <td>—</td>
      <td>Yes</td>
    </tr>

    <tr>
      <td>**SSO / SAML**</td>
      <td>—</td>
      <td>—</td>
      <td>—</td>
      <td>Yes</td>
    </tr>

    <tr>
      <td>**Onboarding**</td>
      <td>—</td>
      <td>—</td>
      <td>—</td>
      <td>Hands-on</td>
    </tr>

    <tr>
      <td>**Support**</td>
      <td>Community</td>
      <td>Discord</td>
      <td>Email + Discord</td>
      <td>Dedicated</td>
    </tr>
  </tbody>
</table>

<Note>
  The asynchronous workflow-execution rate that higher plans advertise is configured but not yet enforced, so today's effective limit is the per-minute run rate shown above. Credit and rate-limit numbers are pinned to the backend plan configuration; the public pricing page is the place to confirm current figures at checkout. See [plans and pricing](/billing/plans).
</Note>

### Pay your way: BYOK or managed credits

Cost control is part of scaling. ModuleX gives you two billing models, and you can mix them.

<CardGroup cols={2}>
  <Card title="Bring your own keys (BYOK)" icon="wallet">
    Connect your own model and tool provider accounts. The provider bills you directly with no ModuleX markup, so your AI spend stays on your existing accounts.
  </Card>

  <Card title="ModuleX-managed credits" icon="coins" href="/billing/credits">
    Use ModuleX-provisioned providers and pay in [credits](/concepts/credits-billing) — no setup, with usage metered per organization. Managed usage is what your plan's allowance covers.
  </Card>
</CardGroup>

<Note>
  BYOK is presented as available across all plans. Because BYOK usage is billed by the provider, it is not metered in ModuleX credits — it shows up in analytics only. See [credits and metering](/billing/credits).
</Note>

### Deploy where you need it

On the Enterprise plan, ModuleX can run on your own infrastructure, with single sign-on for your identity provider.

<CardGroup cols={2}>
  <Card title="SSO and SAML" icon="lock" href="/enterprise/deployment-sso">
    Sign in through your identity provider. SSO and SAML are Enterprise-plan capabilities. See [deployment and SSO](/enterprise/deployment-sso).
  </Card>

  <Card title="Self-hosted deployment" icon="server" href="/enterprise/deployment-sso">
    Run ModuleX in your own environment for full control over where your data and runs live, with custom rate limits and credits.
  </Card>
</CardGroup>

## What the Enterprise plan adds

The Enterprise plan is for organizations operating at scale. Its capabilities, as listed on the public Enterprise offering, are:

<CardGroup cols={2}>
  <Card title="SSO and SAML" icon="lock">
    Sign in through your identity provider.
  </Card>

  <Card title="Self-hosted deployment" icon="server">
    Run ModuleX in your own environment.
  </Card>

  <Card title="Custom rate limits and credits" icon="sliders-horizontal">
    Limits and allowances sized to your workload instead of fixed plan tiers.
  </Card>

  <Card title="Advanced analytics and audit logs" icon="chart-line">
    Deeper usage visibility for the organization. Detailed audit-log scope is TBD pending [trust and compliance](/security/trust).
  </Card>

  <Card title="Dedicated support" icon="headset">
    A dedicated support channel for your team.
  </Card>

  <Card title="Hands-on onboarding" icon="graduation-cap">
    Guided onboarding to get your organization running.
  </Card>
</CardGroup>

<Note>
  Enterprise pricing is custom. The capabilities above mirror the public Enterprise offering; the Free, Pro, and Max plans are self-serve. For a side-by-side of every plan, see [plans and pricing](/billing/plans), and for the SSO and self-hosting reference, see [the Enterprise security page](/security/enterprise).
</Note>

## Trust and compliance

Security is covered in depth in its own [security overview](/security/overview): the [authentication model](/security/authentication), [organization context](/security/org-context), [roles and permissions](/security/roles-permissions), and [data security and encryption](/security/data-encryption).

<Warning>
  This research base does not pin any formal compliance certification (for example SOC 2, ISO 27001, or specific regulatory programs), and ModuleX's published terms state the service is not designed for use under regulated regimes such as HIPAA, GLBA, or PCI-DSS. Do not assume a certification that is not confirmed. The authoritative, current statement of compliance posture and sub-processors lives on [trust and compliance](/security/trust), [compliance](/security/compliance), and [sub-processors](/security/sub-processors) — treat any certification claim as **TBD** until it appears there.
</Warning>

## Built on org-scoped access

Everything above rests on one idea: each request acts inside exactly one organization. When your team works programmatically, every call carries the API key plus the organization it acts on — the same governance boundary you see in the app. Authentication uses `Authorization: Bearer mx_live_…` together with the `X-Organization-ID` header; see [authentication](/api-reference/authentication).

The example below lists the workflows in one organization. Swap the organization id to act inside a different tenant — the access boundary travels with the header.

<CodeGroup>
  ```bash cURL theme={null}
  curl https://api.modulex.dev/workflows \
    -H "Authorization: Bearer mx_live_your_api_key" \
    -H "X-Organization-ID: org_your_organization_id"
  ```

  ```python Python theme={null}
  from modulex import Modulex

  client = Modulex(api_key="mx_live_your_api_key")

  workflows = client.workflows.list(
      organization_id="org_your_organization_id",
  )
  for workflow in workflows:
      print(workflow.id, workflow.name)
  ```

  ```javascript JavaScript theme={null}
  import { Modulex } from "modulex-js";

  const client = new Modulex({ apiKey: "mx_live_your_api_key" });

  const workflows = await client.workflows.list({
    organizationId: "org_your_organization_id",
  });
  for (const workflow of workflows) {
    console.log(workflow.id, workflow.name);
  }
  ```
</CodeGroup>

For the full developer surface, see the [API overview](/api-reference/overview) and the [SDKs overview](/sdks/overview).

## Common questions

<AccordionGroup>
  <Accordion title="How is an organization different from a personal account?" icon="building">
    An organization is the tenant and billing unit. Workflows, runs, credentials, knowledge bases, and the credit wallet all belong to an organization, and access is decided by org roles. You can belong to more than one organization and switch between them. See [organizations, roles and membership](/concepts/organizations-roles).
  </Accordion>

  <Accordion title="Who can build and run the AI surfaces?" icon="user-check">
    The agentic surfaces — the AI Composer, the Assistant, knowledge management, and schedules — require the **owner** or **admin** role. The `member` role has been retired. See [roles and permissions](/security/roles-permissions).
  </Accordion>

  <Accordion title="Can we use our own model and tool keys?" icon="key">
    Yes. With BYOK you connect your own provider accounts and the provider bills you directly with no ModuleX markup. You can also use ModuleX-managed credits, and mix the two. See [credits and metering](/billing/credits).
  </Accordion>

  <Accordion title="Can ModuleX run on our own infrastructure?" icon="server">
    Self-hosted deployment is an Enterprise-plan capability, alongside SSO and SAML and custom limits. See [deployment and SSO](/enterprise/deployment-sso) and [the Enterprise security page](/security/enterprise).
  </Accordion>

  <Accordion title="Is ModuleX certified for a particular compliance program?" icon="badge-check">
    Compliance posture and sub-processors are documented on [trust and compliance](/security/trust), [compliance](/security/compliance), and [sub-processors](/security/sub-processors). Any specific certification should be confirmed there rather than assumed; this research base does not pin one.
  </Accordion>

  <Accordion title="How do we get an Enterprise plan?" icon="handshake">
    Enterprise pricing is custom. Tell us about your team and we will follow up. See [contact sales](/enterprise/contact-sales).
  </Accordion>
</AccordionGroup>

## Talk to the team

If your organization needs custom limits, self-hosting, SSO, or hands-on onboarding, the Enterprise plan is built for you.

<Card title="Contact sales" icon="handshake" href="/enterprise/contact-sales">
  Tell us about your team — size, the tools you use, and what you want to automate — and we will help you find the right plan. Enterprise pricing is custom.
</Card>

<CardGroup cols={2}>
  <Card title="Plans and pricing" icon="tags" href="/billing/plans">
    Compare Free, Pro, Max, and Enterprise side by side, including allowances and limits.
  </Card>

  <Card title="Enterprise security" icon="shield" href="/security/enterprise">
    SSO, self-hosting, seats, and support, for larger teams.
  </Card>

  <Card title="Security overview" icon="lock-keyhole" href="/security/overview">
    How ModuleX secures your data, credentials, and access.
  </Card>

  <Card title="Deployment and SSO" icon="server" href="/enterprise/deployment-sso">
    Single sign-on and self-hosted deployment options for enterprise.
  </Card>
</CardGroup>