ModuleX for enterprise

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.

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.

Build together

Your team co-edits the same workflow on a live canvas, runs from chat, API, or SDK, and shares one knowledge base — instead of passing files and prompts around.

Govern access

Every workflow, run, credential, and knowledge base belongs to an organization. Owner and admin roles decide who can build, connect tools, and run agentic surfaces.

Scale usage

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.

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.

Collaboration: your team works on one canvas

Most automation tools assume one builder. ModuleX assumes a team. The workflow builder 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.

Live co-editing

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.

One shared workspace

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.

Build with AI, together

The AI Composer turns a plain-English description into an editable workflow graph your team can refine — a fast shared starting point, not a black box.

Shared chats

Keep conversations personal, or make them organization-visible so teammates can pick up, review, and continue the work.

Live team collaboration is available on the Pro, Max, and Enterprise plans; the Free plan is a solo workspace. See plans and pricing for what each plan includes.

For how edits stay in sync across collaborators and external changes, see realtime co-editing and external sync.

Governance: clear ownership over access and data

As more people build, you need to know who can do what. In ModuleX, the organization 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, the Assistant, knowledge management, and schedules — require the owner or admin role.

Owner

Full control of the organization, including billing and membership. The owner can do everything an admin can, plus manage the plan.

Admin

Can build and edit workflows, connect tools, manage knowledge, and run the agentic surfaces. Admins handle day-to-day building and operations.

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.

Credentials stay in the organization

The keys your team connects — the credentials behind every integration — 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.

Org-scoped credentials

Connect a tool once for the organization. Credentials are stored encrypted and never re-exposed after they are saved.

Org context on every request

Programmatic access selects an organization with the X-Organization-ID header, so each call is scoped to exactly one tenant’s data.

For how secrets are encrypted and how access is enforced, see data security and encryption and the full 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. What is firm: usage is metered per organization in credits, 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 and credits and metering for the full picture.

	Free	Pro	Max	Enterprise
Credits	300 (one-time trial)	5,000 / mo	20,000 / mo	Custom
API rate limit	10 / min	100 / min	500 / min	Custom
Workflow execution	10 runs / min	150 runs / min	500 runs / min	Custom
Live team collaboration	—	Yes	Yes	Yes
Self-hosted deployment	—	—	—	Yes
SSO / SAML	—	—	—	Yes
Onboarding	—	—	—	Hands-on
Support	Community	Discord	Email + Discord	Dedicated

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.

Pay your way: BYOK or managed credits

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

Bring your own keys (BYOK)

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.

ModuleX-managed credits

Use ModuleX-provisioned providers and pay in credits — no setup, with usage metered per organization. Managed usage is what your plan’s allowance covers.

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.

Deploy where you need it

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

SSO and SAML

Self-hosted deployment

Run ModuleX in your own environment for full control over where your data and runs live, with custom rate limits and credits.

What the Enterprise plan adds

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

SSO and SAML

Self-hosted deployment

Run ModuleX in your own environment.

Custom rate limits and credits

Limits and allowances sized to your workload instead of fixed plan tiers.

Advanced analytics and audit logs

Deeper usage visibility for the organization. Detailed audit-log scope is TBD pending trust and compliance.

Dedicated support

A dedicated support channel for your team.

Hands-on onboarding

Guided onboarding to get your organization running.

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, and for the SSO and self-hosting reference, see the Enterprise security page.

Trust and compliance

Security is covered in depth in its own security overview: the authentication model, organization context, roles and permissions, and data security and encryption.

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, compliance, and sub-processors — treat any certification claim as TBD until it appears there.

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. 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.

curl https://api.modulex.dev/workflows \
  -H "Authorization: Bearer mx_live_your_api_key" \
  -H "X-Organization-ID: org_your_organization_id"

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)

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);
}

For the full developer surface, see the API overview and the SDKs overview.

Common questions

How is an organization different from a personal account?

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.

Who can build and run the AI surfaces?

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.

Can we use our own model and tool keys?

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.

Can ModuleX run on our own infrastructure?

Self-hosted deployment is an Enterprise-plan capability, alongside SSO and SAML and custom limits. See deployment and SSO and the Enterprise security page.

Is ModuleX certified for a particular compliance program?

Compliance posture and sub-processors are documented on trust and compliance, compliance, and sub-processors. Any specific certification should be confirmed there rather than assumed; this research base does not pin one.

How do we get an Enterprise plan?

Enterprise pricing is custom. Tell us about your team and we will follow up. See contact sales.

Talk to the team

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

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.

Plans and pricing

Compare Free, Pro, Max, and Enterprise side by side, including allowances and limits.

Enterprise security

SSO, self-hosting, seats, and support, for larger teams.

Security overview

How ModuleX secures your data, credentials, and access.

Deployment and SSO

Single sign-on and self-hosted deployment options for enterprise.

​From one person to a whole organization

Build together

Govern access

Scale usage

​Collaboration: your team works on one canvas

Live co-editing

One shared workspace

Build with AI, together

Shared chats

​Governance: clear ownership over access and data

​Roles that map to responsibility

Owner

Admin

​Credentials stay in the organization

Org-scoped credentials

Org context on every request

​Visibility over usage

​Scale: grow run rates, usage, and deployment

​Pay your way: BYOK or managed credits

Bring your own keys (BYOK)

ModuleX-managed credits

​Deploy where you need it

SSO and SAML

Self-hosted deployment

​What the Enterprise plan adds

SSO and SAML

Self-hosted deployment

Custom rate limits and credits

Advanced analytics and audit logs

Dedicated support

Hands-on onboarding

​Trust and compliance

​Built on org-scoped access

​Common questions

​Talk to the team

Contact sales

Plans and pricing

Enterprise security

Security overview

Deployment and SSO

From one person to a whole organization

Collaboration: your team works on one canvas

Governance: clear ownership over access and data

Roles that map to responsibility

Credentials stay in the organization

Visibility over usage

Scale: grow run rates, usage, and deployment

Pay your way: BYOK or managed credits

Deploy where you need it

What the Enterprise plan adds

Trust and compliance

Built on org-scoped access

Common questions

Talk to the team