A pull-based event queue with explicit ACK/FAIL state. Track every webhook across any cloud or region. Simple HTTP ingestion, no magic, byte-correct.
Looking for a few teams to try it and share feedback
Explicit processing state, not delivery guarantees. Works across any cloud, any region.
Stripe webhooks arrive twice. AWS Lambda retries. GCP Functions span regions. You handle duplicates—every single time.
POST webhooks to ackstate. Your code pulls when ready. Mark each with ACK (success) or FAIL (error).
GCP Pub/Sub exactly-once works only within a single region. AWS Lambda idempotency requires per-function configuration.
Deploy across regions or cloud providers. Single source of truth for event state everywhere.
Every team builds their own ledger—database tables, Redis sets, idempotency keys. Same logic, different implementation.
One HTTP endpoint. Full visibility into every event state. No rebuilding per service.
Events recorded → Pulled by your app → ACK/FAIL state
Complements your existing tools. Doesn't replace them.
Stripe delivers webhooks at least once. Deduplicate, track payment events, and replay without hitting rate limits.
Deploy across AWS Lambda regions or GCP Cloud Functions zones. Single source of truth for event state everywhere.
Send JSON, protobuf, or raw bytes. We don't parse or validate—your application decides what the data means.
We're looking for a few teams building real webhook workflows to try ackstate and share feedback. Direct access to the team, no marketing noise.
Invite-only · Early access · Help shape the product