Projects are the organizational unit in Gateway. Every project has a unique slug, its own budget, routing policy, and compression settings. Requests are scoped to a project via the X-Project-Id header. Projects are the foundation — routing, compression, budgeting, and spend tracking all attach to a project.
Create a project from the Gateway dashboard using the four-step wizard:
X-Project-Id value), and optional description.All settings are editable after creation. Projects can be deactivated without deleting.
Pass the X-Project-Id header with the project slug. Without it, requests use org-level defaults.
Each project can have a budget that caps spend for a billing period. How Gateway enforces that cap depends on the enforcement mode:
Alert thresholds default to 50%, 80%, and 90% of the budget. The dashboard shows color-coded progress bars: blue (< 80%), yellow (80–100%), red (100%+).
For complete coverage of budgets, billing, and cost-saving strategies, see Cost Governance and Savings.
Tags are key-value pairs defined at the org level. They serve two purposes:
customer_tier: enterprise to a quality-first policy. See Routing Policies for configuration details.The dashboard includes quick-fill templates for common tags like customer_tier, environment, and region.
Yes. Separate projects by environment, team, or product feature to get independent budgets, routing, and spend tracking for each.
Requests use org-level defaults for routing and compression. Spend is tracked at the org level and not attributed to any project.
No. The slug is used in API headers and spend tracking and cannot be changed. All other settings are editable.
Yes. Deactivating a project stops it from accepting requests but retains its configuration and history.
Projects define static configuration — budget, routing policy, compression settings. Tags are dynamic per-request metadata used for routing decisions and spend tracking within a project.