Core model
How organizations, projects, and environments fit together in TxnShield.
Organization
An organization is the tenant boundary for billing, members, roles, usage, audit logs, alerts, and webhooks. Most plan limits are enforced at this level.
Use one organization for one company or customer account. Do not put unrelated customers in the same organization unless they share billing and administration.
Project
A project represents an application, service, or product surface that sends protected transaction events. A project groups environments and keeps configuration understandable as your integration grows.
Create separate projects when the applications have different teams, release cycles, or protected workflows.
Environment
An environment is the runtime boundary for keys, protected operations, policies, events, decisions, and activation. Development, staging, and production should use separate environments and separate keys.
Production environments are a paid entitlement because they unlock live enforcement posture and operational controls.
How they connect
- Members belong to organizations and receive permissions through roles.
- Projects belong to organizations and count toward project limits.
- Environments belong to projects and carry the actual runtime configuration.
- Events, decisions, keys, protected operations, and policies are scoped to one environment.
Next steps