Setup guidance for OggyCloud integrations.
Use these notes to understand provider access patterns, support levels, and current product boundaries before connecting billing or API credentials.
Integration support levels
OggyCloud labels each integration by current support level so teams know what can sync today.
Real sync
Credentials are validated and OggyCloud imports useful resources, billing, or telemetry.
Partial sync
Credentials are validated, but accurate analytics depend on provider exports or limited API coverage.
Connection-only
Credentials can be stored and connection state can be shown, but telemetry ingestion is not implemented yet.
Connection guides
AWS
Connect with a read-only IAM role. Use CUR/S3 for production-grade historical billing analytics.
GCP
Connect with a service account. BigQuery Billing Export is required for accurate historical cost data.
Azure
Connect with an app registration and Cost Management Reader permissions.
Vercel
Connect with a team or personal API token to sync projects, deployments, and selected runtime signals.
MongoDB Atlas
Connect with Atlas API credentials. Project sync is available; cluster and billing depth expand as adapter coverage grows.
AI providers
OpenAI, Anthropic, Gemini, and OpenRouter setup guidance is available; deeper usage tracking depends on telemetry or gateway ingestion.
Security boundaries
Use read-only provider access where possible. Avoid root credentials. Prompt and response logging for AI usage remains opt-in and policy controlled.
For detailed provider-specific setup steps, keep the repository guide updated:
Open integration directory