Idea to Production
Book a call

Integrations

Everything your application can already do.

Payments, accounting, identity, messaging, signatures, support and analytics — built into the platform, connected to the services businesses actually use.

  • 24 connections live
  • 13 categories
  • Off until you need them
  • Anything else on request

Nobody starts with single sign-on. You start with an idea and no customers, and everything on the enterprise checklist is someone else's problem — until, quite suddenly, it is yours.

So none of it is switched on. Your application inherits the capability from the first line, and stays out of your way until the day you need it. When that day comes, it is a toggle — not a project, not a rebuild, and not a conversation about what it will cost to add.

See how capability arrives as you grow

The catalogue

Thirteen categories, one switch each

Available means built and running today. On request means we build it for your application. Every card says which, because the distinction is the useful part.

Payments, billing & tax

Take money, on the rails your customers use

  • Stripe
  • Stripe Billing
2 available +8 on request

Accounting & ERP

Money that reconciles without retyping

  • Xero
1 available +5 on request

Identity, access & audit

Their directory, their rules, their audit trail

  • Google Workspace
  • Microsoft accounts
  • Multi-factor authentication
3 available +8 on request

Email delivery

Mail that reaches the inbox

  • Mailgun
  • SendGrid
2 available +3 on request

SMS & voice

Reaching people who are not at a desk

  • Twilio
  • ClickSend
2 available +3 on request

Electronic signature

Agreements signed inside the workflow

  • BoldSign
  • DocuSign
2 available +2 on request

Support & customer chat

Help, in context, where the user is

  • Tidio
  • Intercom
2 available +4 on request

Service management & ticketing

Requests that follow the customer’s own process

  • ServiceNow
  • Jira Service Management
  • Jira Software
3 available +4 on request

Analytics & data

Know what people actually do

  • Google Tag Manager
1 available +10 on request

CRM & sales

One version of the customer

On request

Workplace & documents

Where your team already works

On request

AI models & agents

Models chosen for the job, with limits

  • Anthropic Claude
  • OpenAI
  • pgvector
3 available +4 on request

Connect anything else

The escape hatch, and it is not an afterthought

  • Public REST API
  • Outbound webhooks
  • Scheduled imports & exports
3 available +4 on request

Delivered, not connected

Things we build rather than plug in

These are not third-party integrations. They are parts of your application that exist because your customers, and their security teams, will eventually ask for them.

A help centre your customers actually find

Generated from the application itself, published on your domain, searchable and indexed. It carries the release notes, feeds the weekly digest that tells your customers what you shipped, and answers your support chatbot — without your team in the loop.

  • Documentation produced from the application, not written separately
  • Release notes per release, in customer language
  • A weekly or monthly digest emailed to your customers
  • Full-text search, indexed for search engines and AI assistants
  • The source your support chatbot answers from, with citations

Read more

A developer portal for your customers

When your own customers want to integrate with you, they need somewhere to go: API reference, authentication, sandbox keys, worked examples and changelog. We build and host it alongside your application, on your domain.

  • Documented REST API with authentication and versioning
  • Self-serve API keys, scoped and revocable
  • Sandbox environment with throwaway data
  • Webhook reference with signature verification
  • Changelog, so integrators are not surprised

A status page that proves uptime

Public, on your domain, backed by external monitoring. When something is wrong your customers get a page that says so instead of your inbox getting the question forty times — and when a buyer asks you to evidence your SLA, the history is already published.

  • External uptime checks via UptimeRobot
  • Public status page on your own domain
  • Incident history, kept rather than quietly deleted
  • Uptime percentage over time, as SLA evidence
  • Subscribers notified automatically during an incident

Not on the list

If it has an API, your application can use it

The catalogue records what we have already built, not the limit of what is possible. Tell us the service and you will get a straight answer — including when the answer is that it cannot be done.

How connecting anything works We can also build your website

  • A documented, versioned REST API on your product
  • Outbound webhooks with retries and delivery logs
  • Scheduled file exchange for systems with no API
  • Zapier and Make for the long tail
  • An honest no when a vendor forbids it

Start here

Tell us what you want. In a sentence.

A 30-minute call is enough for us to tell you whether we can build it, what it will cost to run, and when it goes live.

Book a call See how it works