Core concepts
Use this section to understand how OngoingAI Gateway works before you tune configuration or enforce production policy. You will learn how request forwarding, trace capture, privacy controls, and tenant boundaries fit together.
Use this section when
- You are designing a gateway deployment or rollout plan.
- You need a shared architecture model across platform, security, and application teams.
- You need to reason about privacy and tenant isolation behavior before enabling advanced controls.
Read in this order
- Architecture for request-path and trace-path fundamentals.
- Traces and audit model for data model and event boundaries.
- Privacy model for storage and redaction behavior.
- Keys, workspaces, and tenancy for identity scope and isolation rules.
What you should understand after reading
- Where auth, capture, routing, and storage happen in the request lifecycle.
- Which trace data is always captured and which data is optional.
- How privacy controls change persisted trace content.
- How org and workspace scope is applied to access and analytics.