Flintwake
Sign inStart free

Platform

One platform for the half of your product that other people write code against.

Capture, analytics, keys, limits, webhooks, documentation and SDKs. Separately they are six tools and a wiki page. Together they are the thing your integrators experience as your API.

  • 48.2MRequests captured dailyAcross the demo account's three environments
  • 112msp95 at the edgeMeasured from first byte in to last byte out
  • 0.21%Error rateEvery failure attributed to an endpoint and a consumer
  • 34Connected destinationsAlerting, data warehouses, incident tooling

Pillars

What the platform actually does.

  • 01

    Capture every request as a wake

    See observability

    A wake is the full record of one call: request, response, timing breakdown, consumer, key, region and the downstream effects it triggered. Searchable for 30 days, replayable against any environment.

    • Structured capture at the edge, not in your app
    • Bodies redacted by rule before they leave your network
    • Replay a production failure against staging in one click
  • 02

    Read the API by consumer, not by service

    Open the console

    Every metric slices by the integration that produced it. You see which customer is hitting the timeout, which key is burning the quota and which SDK version is still sending the deprecated field.

    • Per-consumer latency, errors and quota
    • Deprecation tracking down to the SDK release
    • Quota warnings fired before the consumer notices
  • 03

    Ship keys, webhooks and limits without a ticket

    Explore the platform

    Scoped keys per environment, signed webhook delivery with automatic retry and replay, and rate limits you can change per consumer — all from the same console, all audited.

    • Scoped keys with one-click rotation and grace windows
    • Signed deliveries, exponential retry, manual replay
    • Per-consumer limit overrides with an audit trail
  • 04

    Docs that are generated from the same source

    Browse the reference

    The reference, the SDK snippets and the playground all read one schema. When an endpoint changes, the docs change with it and the changelog entry writes itself.

    • Reference generated from the live schema
    • Seven SDKs with matching examples
    • Playground calls the same fixtures your consumers test against

How it works

One hop at the edge. Nothing in your hot path.

Flintwake runs as a lightweight edge collector in front of your API, or as a sidecar beside it. It observes, redacts and forwards — it never becomes the thing that has to be up for your API to answer.

  • Fails open: if the collector cannot write, your request still answers.
  • No proxying of request bodies to a third region.
  • Every capture rule is versioned and reviewable in Git.
  1. 01

    Observe

    The collector reads the request and response as they pass. Median added latency is under 2ms.

  2. 02

    Redact

    Field rules strip secrets and personal data before anything leaves your network boundary.

  3. 03

    Capture

    The wake is written to your chosen region with your chosen retention. Failures fail open.

  4. 04

    Resolve

    Explore, attribute, replay and alert — then push the result into the tools your team already uses.

Deployment

Four ways to run the collector.

Pick whichever fits the architecture you already have. All four read the same rule file and produce the same wakes.

  • No change to application code
  • Rules versioned in your own repository
  • Region chosen per project
  • Fails open under every failure mode
Collector deployment
# A standalone process in front of your API.
docker run -d --name flintwake \
  -e FLINTWAKE_API_KEY=$FLINTWAKE_API_KEY \
  -e FLINTWAKE_ORIGIN=https://api.internal.acme.dev \
  -e FLINTWAKE_REGION=eu-central-1 \
  -p 8080:8080 flintwake/collector:4

Surfaces

Everything in the platform, grouped.

  • Traffic

    What is actually happening at the edge, second by second.

    • Request explorer

      Filter 30 days of wakes by method, status, endpoint, consumer, key or region.

    • Response inspector

      Headers, body, timing waterfall and the wake ID your support team can quote back.

    • Endpoint health

      p50 / p95 / p99, error rate and throughput per endpoint, sorted by whatever is hurting.

    • Live tail

      A rolling stream for the twenty minutes around a deploy.

    • Geography

      Latency split by edge region so you know whether it is you or the distance.

  • Reliability

    Turning a spike into an owner, a cause and a fix.

    • Error attribution

      Every non-2xx grouped by code, endpoint, consumer and deploy.

    • Replay

      Re-run any captured request against staging and diff the response.

    • SLO tracking

      Availability and latency objectives per endpoint with burn-rate alerts.

    • Deploy markers

      Charts annotated with the release that shifted the line.

    • Anomaly watch

      A quiet statistical baseline that pages you only when the shape genuinely changes.

  • Access

    Keys, scopes, quotas and the audit trail underneath them.

    • Scoped API keys

      Per-environment keys with explicit scopes and a visible last-used time.

    • Rotation with grace

      Issue the replacement, keep both valid for a window, revoke on schedule.

    • Rate limits

      Defaults per plan, overrides per consumer, headers your SDKs already understand.

    • Consumer directory

      Every integration with its plan, quota, error rate and owner.

    • Audit log

      Who changed which key, limit or webhook, from where, and when.

  • Delivery

    The half of an API that runs outbound.

    • Webhook endpoints

      Per-consumer endpoints with event-type subscriptions.

    • Signed payloads

      Timestamped HMAC signatures with a verification snippet in every SDK.

    • Retry and replay

      Exponential backoff, dead-letter after eight attempts, one-click manual replay.

    • Delivery stream

      Every attempt with its response code, duration and payload.

    • Endpoint health

      Automatic disablement of endpoints that have returned 410 for a week.

  • Developer experience

    What your consumers touch before they ever talk to you.

    • Hosted documentation

      Concepts, guides, quickstart and a reference that is generated, not written.

    • API playground

      Authenticated calls against sandbox fixtures, straight from the docs page.

    • Seven SDKs

      TypeScript, Python, Go, Ruby, PHP, Java and Rust with matching examples.

    • Copyable examples

      Language tabs on every snippet, with the consumer's own key pre-filled.

    • Changelog feed

      An RSS feed and a webhook so integrations hear about changes first.

  • Operations

    The things that make a platform team trust a platform.

    • Status page

      Component-level health with a 90-day history and subscribable incidents.

    • Data residency

      US, EU and AP processing regions, chosen per project.

    • Redaction rules

      Field-level rules applied at the edge before capture.

    • Retention control

      7, 30 or 90 days, set per environment.

    • Export

      Stream wakes to S3, BigQuery, Snowflake or your own object store.

See it with your own traffic shape.

Thirty minutes with an engineer, or four minutes with the quickstart. Both end with wakes on a screen.

Talk to an engineerRead the quickstart