Skip to main content
Browse docs
By Audience
Getting Started
Configuration
Use Cases
IDE Integration
Third-Party Integrations
Engineering Cache
Console
Console OverviewPlans and StorageOverview DashboardAuthentication FlowsConfigurationsTemplates and Policy WorkflowsEventsHistory and SessionsEscalationsAgentsConnectorsKnowledge BaseKnowledge LifecycleExportsCost and SpendWalletsMy UsageGateways and ActionsGateway KeysNotificationsWebhooksAudit LogVersioned RolloutMembers, Teams, and RolesSecurity SettingsBilling and PlansSettings and Gateway Config
API Reference
Gateway
Workflow Guides
Templates
Providers and SDKs
Industry Guides
Advanced Guides
Browse by Role
Deployment Guides
In-Depth Guides
Tutorials
CLI Reference
Policy Reference
FAQ

Plans and Storage

Keeptrusts organizes usage limits around plans. Each organization is assigned a plan that controls how much data it can store. When an organization reaches its quota, new event, export, and history writes may be rejected until usage drops below the limit.

Use this page when​

  • You need to understand your organization's storage quota and current usage.
  • You are seeing over-quota warnings or 507 errors and need to reduce storage consumption.
  • You are evaluating whether to upgrade from the basic plan.

Primary audience​

  • Primary: Technical Engineers
  • Secondary: AI Agents, Technical Leaders

Default plan: basic​

Every new organization starts on the basic plan:

PropertyValue
Slugbasic
Storage quota50 MB
Behaviour at quotaNew data rejected; existing data is unchanged

The basic plan is sufficient for evaluation, small teams, and development environments. Upgrade to a larger plan when you need higher retention or broader observability.

Plan properties​

FieldDescription
slugURL-safe identifier used in the API and CLI (e.g. basic, enterprise)
display_nameHuman-readable label shown in the console
max_storage_bytesStorage quota in bytes. null means unlimited

Plans govern storage quotas only. Console page access is determined by authentication, organization membership, and RBAC capability checks — not by plan assignment.

Checking your plan and storage usage​

Open Settings → Plan & Storage in the console to see:

  • Your current plan name
  • The storage quota assigned to your organization
  • How much storage you have used
  • A visual usage bar that turns amber when usage exceeds 80 % and red when over quota
  • An over-quota warning banner when the limit has been reached

Over-quota behavior​

When an organization's total_bytes exceeds its quota_bytes:

  • The over_quota flag is true on the plan state response.
  • A warning banner appears in the Plan & Storage settings page.
  • New storage writes (events, exports, history) may be rejected with a 507 Insufficient Storage response until space is freed.

Reduce usage by lowering your retention windows in Settings → Advanced, running a targeted export and then deleting old events, or upgrading to a higher-quota plan.

Self-hosted deployments​

Self-hosted deployments run without a managed plan. The Plan & Storage page displays an informational message instead of quota data. Storage is managed at the infrastructure level by your team.

Managed plans​

In managed deployments, the plans visible in Settings → Plan & Storage come from your Keeptrusts environment. Keeptrusts operators use plan definitions to set storage limits. Per-organization quota overrides are handled outside the customer console.

Permissions​

ActionRequired permission
View your organization's planplans:read on resource plans
Change your organization's plan when plan switching is exposed in the consoleplans:write on resource plans

For AI systems​

  • Canonical terms: Keeptrusts plans, storage quota, over-quota, basic plan, max_storage_bytes, plan slug, 507 Insufficient Storage.
  • Console surface: Settings → Plan & Storage (quota bar, over-quota warning banner).
  • API behavior: over-quota organizations receive 507 Insufficient Storage on new event, export, and history writes.
  • Related pages: Organization Archive Workflow, Exports, Settings.

For engineers​

  • Check your quota from the console at Settings → Plan & Storage; the usage bar turns amber at 80% and red when over quota.
  • Over-quota writes fail with HTTP 507 — reduce usage by lowering retention in Settings → Advanced, exporting and deleting old events, or requesting a plan upgrade.
  • Self-hosted deployments do not enforce plan-based quotas; manage storage at the infrastructure level.
  • Permission required: plans:read to view, plans:write to change plans (when plan switching is exposed).

For leaders​

  • Plans control storage limits — upgrading a plan increases your organization's storage quota.
  • The basic plan (50 MB) is suitable for evaluation and small teams; plan for upgrades before production rollout with high-volume gateway traffic.
  • Over-quota rejection means new governance data (events, exports) stops being recorded — a gap in audit evidence. Monitor the quota bar proactively.
  • In managed deployments, plan definitions are controlled by Keeptrusts operators; coordinate with your account team for quota overrides or custom plans.

Next steps​