Integrations
The services we know properly
Any integration works on the happy path. These pages cover the rest: signature verification, duplicate events, out of order delivery, retries, dead letter queues and reconciliation.
- Integrations
- 8 documented in depth
- Also
- We integrate with systems beyond this list through whatever interface they expose
Reference
Integration pages
- StripeCheckout, Payment Intents, subscriptions and Connect payouts, integrated so card data never reaches your systems and every order is created by a verified webhook.
- SupabaseAuthentication, row level security, storage and realtime over managed PostgreSQL, with policies as the authorisation layer rather than checks scattered through code.
- NeonServerless PostgreSQL with branching, used for preview environments that carry their own data and for workloads that idle between bursts.
- GroqLow latency inference over open models, integrated with typed tool calling, grounded retrieval, schema validated output and provider fallback.
- n8nSelf hosted workflow orchestration for cross system automation, with idempotent steps, error branches, run history and credentials held in your own environment.
- ResendTransactional email with authenticated domains, typed templates, idempotent sending, and delivery events written back against the customer record.
- PrintfulPrint on demand fulfilment connected to paid orders, with variant mapping, order references, tracking and deliberate handling of uncertain submission results.
- WordPress and WooCommerceHeadless content and commerce over WordPress and WooCommerce, keeping the editing experience your team knows while the front end and the integrations are yours.
Standard
What every integration we build includes
These are not extras. An integration without them will fail quietly and be discovered by a customer.
| Signature verification | Computed over the raw request body in constant time, with a timestamp tolerance so a captured request cannot be replayed |
|---|---|
| Deduplication | Events stored by provider identifier and processed once, because providers retry and some deliver twice by design |
| Idempotency | Write requests carry a key derived from the business operation, so a retry after a timeout returns the original result |
| Ordering | Transitions compare an event against the state already applied, so a late event cannot revert a newer one |
| Retries | Exponential backoff with jitter, and a circuit breaker so a failing provider is not hammered |
| Dead letter queue | Anything that exhausts its budget is stored with its payload and error, visible and replayable |
| Reconciliation | A scheduled comparison between systems, because a missed event emits no signal |
| Secrets | Held in a platform secret store, scoped per environment, with a documented rotation procedure |
Let’s talk about the system you need.
Tell us where the current process breaks down. We can map the workflow, examine the integration requirements and define a practical scope for the build.
- A mutual NDA is signed before project details are shared.
- Scope is fixed in writing before any build starts.
- You own the source code, the IP and the documentation at delivery.
- Support plans are available and tailored on a discovery or technical call.