Quick start
Get telemetry flowing into InfraSage in under 5 minutes.
There are two modes. Pick the one that fits your situation:
| Cloud (Hosted) | Self-Hosted | |
|---|---|---|
| Who manages the infrastructure? | InfraSage | Your team |
| How to start? | Sign up at console.infrasage.dev | Contact us for a license and artifacts |
| Best for | POCs, teams, production with no infra overhead | Regulated environments, custom data residency |
Option A: cloud
Start here unless you have a reason not to. It is the right choice for most teams.
Step 1: create your account
Go to console.infrasage.dev and sign up. The Free plan is available immediately, no credit card.
Step 2: create an API key
Once you are logged in:
- Go to Settings → API Keys
- Click Create Key
- Give it a name (e.g.
production-ingest) and pick the scope you need - Copy the key. It is shown once and never again.
Your ingestion endpoint is in the console under Settings → Ingestion.
Step 3: send your first telemetry
Replace <YOUR_API_KEY> and <YOUR_INGESTION_URL> with the values from your console:
curl -X POST https://<YOUR_INGESTION_URL>/api/v1/telemetry \
-H "Content-Type: application/json" \
-H "X-API-Key: <YOUR_API_KEY>" \
-d '{
"service_id": "my-first-service",
"metric_name": "request_latency_ms",
"value": 142.5,
"timestamp": "'$(date -u +%Y-%m-%dT%H:%M:%SZ)'"
}'
Expected response:
{"status":"ok","queued":1}
Step 4: look at your data
Go back to console.infrasage.dev and open the Dashboard. Your metrics show up as they arrive. Anomaly detection starts on its own within 60 seconds of data flowing in.
Step 5: connect your stack
Now point your real telemetry sources at InfraSage:
- OpenTelemetry: configure your OTEL Collector
- Prometheus: set up the OTEL Collector
- AWS CloudWatch: poll CloudWatch metrics
- Kubernetes: ingest cluster events and pod metrics
Option B: self-hosted
A self-hosted deployment runs the full InfraSage stack inside your own cloud account, so the data stays where you put it and everything runs within your existing network perimeter.
Prerequisites
- An active InfraSage license (contact [email protected])
- Access to the InfraSage artifact registry (credentials come with your license)
- A Kubernetes cluster (K8S 1.25+) or equivalent container runtime
Getting started
- Request a license. Email [email protected] or ask through console.infrasage.dev
- Receive artifacts. You get access to signed container images and deployment manifests through the InfraSage private registry
- Deploy. Follow the self-hosted installation guide
- Activate. Apply your license key during setup and connect to InfraSage's activation service
:::tip Evaluating InfraSage? For a proof of concept, the fastest path is signing up for the Cloud plan. There is no infrastructure to set up, and you can send real production metrics within minutes. :::
What's next
- Send more telemetry formats: First Telemetry guide
- Connect your monitoring stack: OpenTelemetry, AWS CloudWatch
- Understand the architecture: Core Concepts
- Review billing and usage: Plans & Pricing