Go have a beer.
We've got the boring bits.

Your app needs email, payments, storage and other services. You don't need another afternoon wrestling with provider setup, API keys and integration code.

Gateman handles supported provider operations and setup work, so you can get back to building.

Two applications. 100,000 monthly operations. Standard for 14 days.

A glass pint of amber beer topped with foam

Less provider faff

You've got better things to build.

02

Take payments without another credential shuffle.

Gateman supports provider-specific operations for Stripe, Square and PayPal. Keep each provider's own request model, with Gateman handling the supported connection and credential plumbing. For Stripe, the supported webhook setup flow creates the endpoint and stores its signing secret for the application—no event-list clicking and secret copying after the fact.

See the Stripe webhook setup
03

Let the photo go straight to storage.

For Amazon S3 and Cloudflare R2, Gateman creates a presigned upload or download request. Your app gets the signed operation; the file travels directly between the browser and storage. No detour through Gateman, and no signing plumbing to build yourself.

See the R2 upload flow
04

Give your coding agent a bounded way to work on provider settings.

When a task involves Cloudflare or AWS configuration, an agent can use the application's enabled, supported provider operations to inspect or make an authorised change. You give it the task and review the work; the provider's own permissions still apply.

See an AI-assisted Cloudflare configuration example
05

SES setup, minus the afternoon in AWS.

Gateman Premium can provision the supported SES workflow across AWS and the related DNS setup, including identities, permissions and tracking. Completed setups have taken as little as three minutes. AWS approval for production sending is still its own step.

See what SES provisioning covers

And that's not the whole list.

Gateman also supports SMS, bot verification, authorised credential retrieval and other provider operations. Browse the full capability reference to see what's available for your application.

A short route to the feature

Set it up. Get on with it.

Create an application in Gateman, choose the supported operations it needs and configure the relevant providers. Connect using an official PHP, Node.js, Python or Go client. Then call the operation your feature needs.

  1. 01Create an application
  2. 02Choose its capabilities and configure providers
  3. 03Connect with an official client
  4. 04Build using the documented operation

Useful context for the next task

Tell your coding agent what to build. Gateman tells it how this app connects.

Give your agent the application-specific bootstrap instructions generated by Gateman. They point it to the official client and the app's current authorised capability context, so it can follow the right implementation guide instead of reconstructing your setup from scratch.

Ask for the feature. Review the code. The agent works from the capabilities you've enabled for that application, with the provider's own permissions still applying.

See the application bootstrap workflow
01Your feature requestWhat you want built
02App-specific bootstrapCurrent capabilities and client guidance
03Implementation to reviewBuilt against the right integration path

Credentials, in their place

Your provider keys can stay put.

For supported mediated operations, the provider credential stays configured at Gateman while your application authenticates to Gateman. If an integration needs the credential itself, you can separately authorise retrieval for that application. Stored sensitive values can be added, replaced or deleted in the console; the console does not reveal an existing value after it has been saved.

Your app's Gateman signing material still belongs in protected server-side configuration. The point is less repeated provider setup and credential plumbing—not pretending credentials no longer need care.

Plans and trial

Start simple. Add provisioning when you need it.

Standard includes Gateman's supported core operations. Premium includes all of Standard, plus eligible managed provisioning and email protection: global hard-bounce suppression, app-scoped complaint suppression, email transaction history, sending anomaly detection and owner alerts. An automatic sending pause is available as an option when explicitly enabled and configured conditions are met.

Monthly plans in US dollars
CapacityStandardPremium
2 apps$15 / month100,000 operations$35 / month100,000 operations
5 apps$29 / month300,000 operations$69 / month300,000 operations
15 apps$59 / month1,000,000 operations$129 / month1,000,000 operations
Additional app+$4 / month+$8 / month
Team Access$10 / monthper block of 5 team members
Start your free Standard trial

A few things worth knowing

Operations

Gateman counts accepted billable operations when they enter execution, not every HTTP request. The allowance is shared across your applications. Once exhausted, further billable operations are rejected until the next period or an allowance change.

Premium

Premium provisioning requires a paid Premium plan. Once Premium provisioning has been used, switching down to Standard is not available.

Different requirements?

Individual commercial agreements may be considered where the published pricing model does not fit a particular application's operating requirements.

Go build the useful bit

Get back to building the thing.

Email, payments, uploads, provider setup: use Gateman for the supported plumbing you'd rather not rebuild.