Skip to content

What is Amlexia?

Amlexia is operational intelligence for modern backends: your HTTP APIs, AI providers (OpenAI, Anthropic, Gemini, …), payments (Stripe), auth (Clerk), messaging, and infrastructure dependencies.

Instrument with Node.js, Python, Go, or Ruby SDKs (or send OpenTelemetry). Events flow to ingest.amlexia.com; your team uses app.amlexia.com for analytics, alerts, and traces.

What you get

CapabilityDescription
Request monitoringLatency, status, errors per route (normalized paths)
Provider intelligenceAuto-detect OpenAI, Stripe, Clerk, etc.
AI / LLM metricsTokens, models, streaming latency, reported + estimated cost
Distributed tracingTrace/span IDs, W3C traceparent, session linkage
Live streamNear-real-time SSE
Smart alertsEmail, Slack, HTTP webhook
Insights & AI summaryBackground analysis + narrative health summary
OperationsSLO-style availability, spend forecast, incidents
Environment viewsFilter and compare production vs staging
Usage meterMonthly event count vs plan (10k free tier)

SDKs

SDKInstall
Node.jsnpm install @amlexiahq/node
Pythonpip install amlexia
Gogithub.com/amlexiahq/amlexia-go
Rubygem install amlexia

Also: Bun, Deno, Cloudflare Workers via the Node package — Bun, Deno & Edge.

How it fits in your stack

Your app  ──SDK──►  ingest.amlexia.com  ──►  Amlexia platform

Your team ──Clerk JWT──►  api.amlexia.com  ◄──  app.amlexia.com
  • Ingest requires your SDK key in each payload.
  • Dashboard API requires Clerk login.
  • Never put the SDK key in browsers or mobile apps.

Who is it for?

  • Teams running Node, Python, Go, or Ruby APIs in production
  • Products heavy on LLM or payment outbound calls
  • Engineers who want one pane of glass without self-hosting Grafana/Jaeger

Architecture

mermaid
flowchart LR
  App[Your app] -->|SDK batch| Ingest[ingest.amlexia.com]
  Ingest --> Platform[Cloudflare Workers + D1]
  You[Your team] -->|Clerk| Dashboard[app.amlexia.com]
  Platform --> Dashboard

Next steps