A BYOK form backend receives your form submissions and then sends them onward using API keys you supply: your Resend key for email, your Google account for Sheets, your signing secret for webhooks. The integrations bill to your accounts at the provider's price, so the form tool has nothing to mark up and no reason to put them behind a paid tier.
Bring your own key, or BYOK, also shows up in cloud key management and AI tools, where it means something related but different. This post is about the SaaS-integration meaning: what it changes for a form backend, how the keys are handled, and what the pricing difference looks like in practice.
What Bring Your Own Key Means
Bring your own key means you supply the API credentials, and the platform uses your keys to do the work on your behalf, instead of reselling you access through its own account.
This is already how most things work at the infrastructure level. You bring AWS credentials to Terraform. You bring a Stripe secret key to your payments library. The tool orchestrates; the provider bills you directly. Nobody adds a margin on top of your Stripe usage. Stripe does the charging.
"You're not paying for the integration. You're paying for the markup on your own API keys."
The opposite model, call it bring-your-wallet, is where the tool holds the keys, makes the calls on its own account, and bills you a marked-up rate for the privilege. BYOK flips that ownership back to you.
Why BYOK Changes the Trust Model
When the keys are yours, the relationship with the tool changes in three concrete ways:
Cost accrues to you, not a middleman. Resend's free plan covers 3,000 emails a month (100 a day) per its pricing page, so most contact forms cost nothing to notify on. There's no integration tier marking up an API you already pay for.
You can leave. Revoke the key and the tool's access ends instantly. Your data isn't hostage to a credential the vendor controls, and there's no migration tax to switch providers.
Security responsibility is explicit. Holding someone's third-party credentials is real responsibility. Good BYOK is verifiable, not just promised:
- Encrypted at rest. Keys are encrypted (OSForms uses AES-256-GCM) before they touch the database, with the encryption key in the environment, not the DB. Dump the database and you get ciphertext.
- Never logged. Decrypted in memory for the call, then discarded. Not in logs, errors, or storage.
- Scoped access. OAuth integrations request the narrowest scope that works. OSForms' Google Sheets integration uses
drive.file, not full-Drive access.
"You don't have to trust a description of how your keys are handled. When the code is open source, you can read the implementation."
How a BYOK Form Backend Works
A form backend is a clean example, because every integration it offers runs on a key you already own. In OSForms, adding one looks like this:
- You paste your API key (Resend, a webhook signing secret) or complete an OAuth flow (Google Sheets).
- The credential is encrypted at rest with AES-256-GCM.
- When a submission arrives, OSForms decrypts it in memory and makes the call.
- The decrypted key is never logged or persisted beyond that execution.
Submission → OSForms → decrypts your key → calls Resend API → logs result
↑
Resend bills your account
The practical payoff shows up on the pricing page. Here's the cheapest generally available plan that unlocks each integration, from each vendor's pricing page in November 2026 (Formspree, Basin, Web3Forms):
| Feature | OSForms (BYOK) | Formspree | Basin | Web3Forms |
|---|---|---|---|---|
| Auto-reply email | Free | $30/mo (Professional) | $24.17/mo yearly (Growth) | $149/yr (Pro) |
| Google Sheets | Free | $15/mo (Personal) | $24.17/mo yearly (Growth) | $149/yr (Pro) |
| Webhooks | Free | $30/mo (Professional) | $24.17/mo yearly (Growth) | $149/yr (Pro) |
| Open source | Yes (MIT) | No | No | No |
| Self-hostable | Yes | No | No | No |
The Google Sheets row runs on your Google account in every column; the paid tiers charge for permission to connect it. For a wider comparison of hosted options, including where each one is the better pick, see Formspree alternatives compared. For a hands-on example, see how to send form email notifications with Resend on your own key, and the docs cover self-hosting if you want to own the whole stack.
BYOK Beyond Form Backends
The form backend is one instance of a pattern worth asking for wherever your data and credentials are involved:
- AI features. Tools that run on your own OpenAI or Anthropic key, so inference cost and prompt data stay on your account, not the vendor's.
- Email and messaging. Resend, Postmark, Twilio: bring the key, pay the provider, skip the per-message markup.
- Analytics and storage. Pipe events and files into infrastructure you control rather than a silo you rent.
The test is simple. If a tool charges you for something that runs on a credential you provide, ask why. BYOK isn't a novel idea; infrastructure tooling has worked this way for years.
OSForms is built entirely on this model. The integrations are free because they cost us nothing to run (you bring the key, you bear the provider cost), and the code is open source so you can verify every word of that. The data side of the same argument, export, deletion, and retention, is in why your form tool shouldn't own your data, and the Google Sheets walkthrough shows BYOK on the integration people ask for most.
Try it free, no card required: osforms.com/signup.
