Getting Started
Itera customer documentation is organized around two tracks:
- Platform docs are required. They explain the core customer integration and the role of
itera.yml. - Inspector docs are optional. They cover the React and Vue component inspector integrations for teams that want deeper component-level visibility.
Recommended reading order
- Start with the Platform Overview to understand the required setup.
- Use this site as the canonical entry point for customer-facing integration guidance.
- Add the Inspector Overview only if your team needs the optional component inspector.
What each track covers
Platform
The platform section is the foundation for every integration. It covers how itera.yml shapes the runtime setup, how Itera connects to your application, and where to look when configuration choices affect behavior.
Inspector
The inspector section is for teams integrating the optional component inspector. It covers the bridge and runtime startup model, React integration, Vue integration, framework-specific entrypoints, and troubleshooting for bootstrap timing, host-origin mistakes, and Vue source metadata.
Managed vs self-managed deployments
When your application is deployed inside Itera-managed infrastructure, Itera infrastructure already injects the documented inspector environment variables during deployment. Teams only need to wire those values into the app themselves for local development or customer-managed deployments outside Itera-managed infrastructure.
Next steps
Move into the platform overview for the required integration path or the inspector overview when your rollout needs the optional component inspector.