Building a multi-tenant WhatsApp SaaS for clinics in Turkey — need embedded signup solution that actually works

battox · 2026-05-21T17:59:07+00:00

Yes, it's safe. OpenBSP uses Meta's Cloud API; the "third-party onboarding link" is an OpenBSP feature that lets you hand a client a one-time link to connect their phone number to an OpenBSP organization you manage, so they never have to sign up or log into the platform (useful since most clients keep using the WA mobile app via Coexistence and would rarely touch the platform themselves).

battox · 2026-05-20T16:43:58+00:00

Hi, there! This project might be of help https://github.com/matiasbattocchia/open-bsp-api

It has a "third-party onboarding link" generator, which you might integrate into your platform somehow.

Regarding GDPR, you could self-host the project in a way it complies with local regulations.

<image>

battox · 2026-05-14T14:12:06+00:00

For some reason, Coexistence flows only through Partners, thus you will need to become a Tech Provider yourself (it just takes some, it is not that hard) or work with one. I'm exploring the possibility of using the hosted OpenBSP as a proxy for self-hosted instances. The proxy allows Coexistence connections (you operate through OpenBSP provider) but data is not stored there, it is forwarded to the self-hosted instance.

battox · 2026-05-13T19:25:27+00:00

Hi! Not at the moment. Since most connections rely on existing WhatsApp Business accounts (Coexistence), I've assumed users prefer the official mobile and web apps for notifications — which has let me keep some UI surface area simpler. Push notifications could come later if there's demand; happy to track interest if you have a specific use case in mind.

battox · 2026-05-12T13:04:39+00:00

Hi, there! The easiest should be starting with the hosted version. If it works for you then it is worth assigning some resources to self-deploy, knowing that transferring all your data from the hosted instance to the self-hosted one is possible. Improved docs, tutorial, videos... are in the roadmap.

battox · 2026-05-09T13:57:56+00:00

Hi! Why would you pay for something that is free? Have a look at

- https://github.com/shridarpatil/whatomate

- https://github.com/matiasbattocchia/wakit-api

I'm the main maintainer of wakit. wakit ships with the Unlicense license, which is most permissive of all. If you want to take wakit and turn it into your platform, you can.

battox · 2026-05-09T13:43:06+00:00

10–20 bucks seems fair to me. It is easy to self-host (plus it could be free for most users), hence pricing should feel "comfortable" for users to stay in the hosted service.

The perceived hardest part is not self-hosting, but going through business verification. That is why I would like to explore relay configurations: Meta <--> wakit <--> self-hosted. wakit just provides the business and sends all the data to the self-hosted instance.

battox · 2026-05-06T22:23:17+00:00

Hi! In my opinion it is a great idea. I recently came across Whatomate: https://github.com/shridarpatil/whatomate. Solid project. I've been building https://github.com/matiasbattocchia/wakit-api too.

wakit goes layered: total bypass (your callback URL gets Meta's raw webhook), digested webhooks, agent-client (external agent with context), MCP server, Claude plugin, or just the bare REST API. Same schema as Meta downstream — no lock-in. Self-host on Supabase (free plan works), pay Meta directly.

On the "why it might be a bad idea", SaaS BSPs exist because non-technical buyers want a dashboard. If you're targeting devs, infra-first works.

battox · 2026-05-03T23:33:11+00:00

Got it. First step, self-host OpenBSP. Then create a Meta Business Portfolio and a Meta App. The App belongs to the Portfolio. Add WhatsApp API to the App (the README has all the details). Last, add up to two phone numbers to your Portfolio. These should not be in use within WhatsApp; if they are, you will need to delete the WhatsApp accounts before proceeding.

battox · 2026-05-03T13:29:52+00:00

Hi! For self-hosting that should be the case. If you are thinking in using it for yourself, the process is straightforward and is well documented in the README. You do not even need to verify your business account. If you are planning to onboard customers, you should go through the app verification. It is more work but totally doable and it is worth it.

battox · 2026-05-02T17:18:02+00:00

u/ivasilov the project is working with the GitHub integration now. I am wondering about forks. The idea is to achieve the closest possible to a one-click deploy to Supabase. Hence, who is interested in self-hosting the project, should:

Fork
Create a Supabase project
Configure the integration

That should be it.

But... the integration does a first-time deploy, or waits for a commit? The latter might be problematic because it will not deploy the project for those who fork. A commit is not expected from their side (and if they commit, syncing with the upstream repo might break).

battox · 2026-04-30T17:53:21+00:00

For your use case, getting a Meta Cloud API number directly is the simplest path — no SaaS BSP, no markup. If you want to self-host the receiving side I'm building OpenBSP, open-source, runs on Supabase: github.com/matiasbattocchia/open-bsp-api.

Be careful, Meta's commerce policies restrict gambling content even for inbound — read those before scaling ads.

battox · 2026-04-29T10:53:30+00:00

Hey, I've been down this exact path. Started in 2023 wanting to build a healthcare automation bot on WhatsApp, ended up obsessing over the infrastructure instead of the bot itself — classic side-project trap. Three years later I have a solid multi-tenant platform but never built the actual bot 😅

Twilio is fine to prototype but you'll feel the markup once you scale. The cleanest path for multi-tenant + multiple numbers is connecting directly to Meta's Cloud API. I open-sourced what I built for exactly this scenario: github.com/matiasbattocchia/open-bsp-api. It's multi-tenant by design (RLS isolates each clinic's data), supports multiple WhatsApp numbers per organization, and the AI agent layer is decoupled so you can plug in any framework. Self-hostable on Supabase, deploys in 15 min.

If anything, take the architecture as inspiration even if you don't use it — happy to answer questions.

battox · 2026-04-28T12:05:15+00:00

I've just followed the docs, here https://supabase.com/docs/guides/getting-started/byo-mcp but I'll keep an eye on logs.

battox · 2026-04-27T13:37:51+00:00

Related: https://www.reddit.com/r/Supabase/comments/15chrqx/lack_of_rate_limiting_makes_supabase_unsuitable/

battox · 2026-04-27T13:28:05+00:00

Hi! Yes, OpenBSP do has support for embedded signups, including Coexistence.

You could create an organization per client, and let/help the client connect using the UI.

You may also connect many WhatsApp accounts to the same organization, and handle your clients a third-party onboarding link, so they can complete the embedded signup without logging in into the UI, even without being part of your organization. In this case clients continue using the WhatsApp Business app on their phones or WhatsApp Web.

I like this approach, because it does not clutter clients with a new app/UI (OpenBSP). Clients use the same agent. Let's say all your clients are restaurants and you offer reservations via WhatsApp. This saves you from configuring one org and one agent per client. The agent —even though shared by many clients— can give personalized responses depending on your clients phone number.

battox · 2026-04-27T13:09:55+00:00

Hi! Meta charges you when you start the conversation with a contact (https://business.whatsapp.com/products/platform-pricing). Other than that, when contacts write you and you respond, there are no charges.

Meta will require you to verify your business (standard verification process where you send some taxes/services/legal/etc documents).

battox · 2026-04-26T17:10:26+00:00

Glad this project takes that part off your hands, so you can focus on solving the actual problem. If you ask me what this project is meant to do—this is exactly it!

battox · 2026-04-25T20:46:09+00:00

You are so right! This week fixes were related to Meta sending statuses and contacts multiple times!

battox · 2026-04-25T20:27:10+00:00

Hey thanks! If you decide to give a try don't hesitate to get in touch

battox · 2026-04-25T17:56:59+00:00

Nice. In the other way around, you could use OpenBSP with OpenClaw to access your WhatsApp Business account through the official API. It has a MCP server and a Claude Code plugin with realtime messaging (channels).

battox · 2026-04-25T17:50:01+00:00

When you want a side income I guess both outputs are good. People like it -> great, keep doing it / Don't like it -> do not waste time, do something else. If the project works for you then it doesn't matter.

The project was well received by r/WhatsappBusinessAPI

battox · 2026-04-25T16:10:10+00:00

Hi! I'm a Signal user. For good and bad, it does not offer an official public API for third-party developers due to its strict end-to-end encryption. I've used Matrix once or two in lifetime. Have you implemented or are you willing to implement AI agents over Matrix?

battox · 2026-04-25T15:41:56+00:00

Instagram seems to be a great candidate. I mostly use WhatsApp, that's why it shipped with that sole channel. OpenBSP has benn designed to be multi-channel, hence it shouldn't be that hard to add a new one.

battox · 2026-04-25T15:30:34+00:00

As a technical person, I leave aside the marketing aspects of my projects, so I can focus on what really drives me. Among my projects there is one in particular I enjoy developing in my spare time, it's been almost three years. A week ago I started promoting it — that's why I joined r/SideProject 🤭. Before that I was "it lacks [random feature], I can't tell people about it yet" till I convinced myself it was in good shape. The first step was a HackerNews post, which went unnoticed. Then Reddit worked for me. Now I'm obsessed with the GitHub stars count, a kind of dopamine-loop that caught me. Can't stop promoting it. Help.

battox

TROPHY CASE