Product and instrumentation
Answers consistent with the current Telemio product and setup model.
What does Telemio collect?
Telemio supports traces, logs, metrics, browser/mobile signals, infrastructure telemetry, and agent runtime metadata through OpenTelemetry-oriented integrations.
Can I use my existing OpenTelemetry instrumentation?
Yes. OpenTelemetry is the default ingestion path. Use your existing SDK or Collector setup where possible, and configure the trusted OTLP endpoint and headers for your workspace.
Do I need to store AI prompts and responses?
No. Agent observability can be metadata-first. Instrument tokens, latency, tools, retries, handoffs, and outcomes without storing prompts or responses by default.
Is there a free plan?
Yes. The current homepage shows a $0 workspace tier with 1 million telemetry units per month, 2 applications, and 7-day retention. Viewer seats are free.
How do organizations and workspaces relate?
An organization can contain multiple workspaces. Access and telemetry are workspace scoped, with separate organization membership and workspace roles.
How does MCP OAuth work?
The supported coding agent or MCP client starts OAuth. The client opens a browser to Telemio consent and sign-in, then receives a scoped access token. Raw clients without a compatible OAuth setup may use a manually created workspace key.
Can I provision Telemio with Stripe Projects?
A Stripe Projects provider integration is in private preview. When enabled for a Stripe account, it is designed to create a Telemio workspace and return trusted OpenTelemetry configuration.
Does this integration analyze my Stripe payments?
No. The Stripe Projects integration provisions observability infrastructure for your software. It is not a Stripe payment analytics integration.
Who can I contact for support?
Email support@wundercorp.co. Never send passwords, bearer tokens, or ingest secrets in a support request.