Skip to content

Docs

Install, configure, and run Marevans.

Same gateway on every cloud: verify at the edge, queue durably, deliver with retries. Choose the guide for your platform below.

Talk to sales

Start here

Core guides.

Deploy

Run in the cloud you already operate.

Marevans ships as containers with reference modules for each major platform. You supply the cluster or compute, TLS certificate, and secrets store.

  • Amazon Web Services
  • Google Cloud
  • Microsoft Azure
  • Kubernetes (any cluster)
  1. Obtain a license for your expected monthly event volume.
  2. Pull the container image and apply the Helm chart or Terraform module for your cloud.
  3. Store provider signing secrets in your vault (SSM, Secret Manager, Key Vault, or Kubernetes secrets).
  4. Expose HTTPS ingress and point a provider sandbox webhook at the URL.
  5. Confirm verified events in the log before switching production traffic.

Sources

Verify before you store.

sources.yaml
yaml
sources:  stripe:    path: /in/stripe    verify:      scheme: stripe      secret: ${vault:/marevans/stripe/signing-secret}      tolerance: 300s

Routing

Fan-out with independent retries.

routes.yaml
yaml
routes:  - name: invoice-paid    match: { source: stripe, type: invoice.paid }    deliver: [billing, analytics]​destinations:  billing:    url: https://billing.internal/hooks/stripe    retry: { max_attempts: 12, backoff: exponential }    on_exhausted: dead_letter

Operations

Dead-letter, replay, and metrics.

Use the event log UI or API to inspect failures, replay by filter, and export OpenTelemetry metrics to your observability stack.

Need help with a production incident? Contact support with event ids and destination names.