Remix vs BYO: choosing your onboarding route
Arino One is the platform — Arino Core — and every client owns and pays for their own Infobip account directly. Arino never bills for messages or acts as a messaging reseller. Onboarding is therefore just two questions: do you already have an Infobip account, and do you want to build the instance yourself or have us build it for you?
Prerequisite for WhatsApp, Instagram, and Messenger: a verified Meta Business Manager. These Meta channels require a verified Meta Business Manager regardless of which route you choose. If you don't have one, Meta Business Verification must be completed before those channels can go connected — Arino can assist with this separately via support. It does not affect the flat $350 setup fee or the optional $50/month Arino Core connection.
The two onboarding routes
| Route | You have an Infobip account? | What happens |
|---|---|---|
| Remix route | No | Register on client.arino.one, confirm by OTP and email, then create your own Infobip account. You own it and pay Infobip directly. |
| BYO route | Yes | Register on client.arino.one, confirm by OTP and email, then connect your existing Infobip account and keys. You continue to pay Infobip directly. |
Both routes end in the same place: you hold your own Infobip account and contract, and Arino One is the platform that sits on top of it.
The two build options
After onboarding, every client picks one of two ways to get a running instance:
| Option | Who builds it | Cost | Best for |
|---|---|---|---|
| Self-build | You (or your developer) via the Lovable template | Free | Teams that want full control, have Lovable experience, or want to customize branding and flows. |
| We build it for you | Arino sets up the instance for you | Flat $350 one-time fee | Teams that want a ready-to-use instance without doing the build themselves. |
Self-build does not require a Lovable subscription from Arino — you work directly in your own Lovable workspace. See remix overview for what remixing means and remix connect instance if you want Arino to help manage a remixed instance later.
The optional Arino Core connection
After your instance is built, the $50/month Arino Core connection is optional:
- With the connection: you stay connected to Arino for WebRTC in-browser calling at $0.009/minute, support, management, and updates.
- Without the connection: you keep the instance, but it is not connected to Arino and receives no Arino support or updates.
This is a real choice: some teams prefer full independence and no recurring platform fee; others want Arino to stay connected for support and WebRTC. See billing and plans for the full rate card and support and SLAs for what the connection includes.
What you pay for, and what you don't
- Infobip usage: paid directly to Infobip by you, in every route.
- Meta fees: paid directly to Meta (for WhatsApp conversation fees, for example).
- Lovable subscription: if you self-build, you pay Lovable directly for hosting if your plan requires it; Arino does not mark this up.
- Arino setup: only if you choose We build it for you — flat $350 one-time.
- Arino Core connection: optional $50/month after build.
Arino is never in the middle of your messaging bill. That makes costs transparent and lets you use your own Infobip volume rates or contract terms.
Choosing quickly
- No Infobip account yet and want Arino to handle the build? Remix route + We build it for you.
- No Infobip account yet and want to customize everything yourself? Remix route + Self-build.
- Already have Infobip and want a ready-to-use instance? BYO route + We build it for you.
- Already have Infobip and want full control? BYO route + Self-build.
After the instance is live, add the $50/month Arino Core connection if you want WebRTC, support, and managed updates; leave it off if you prefer to run independently.
Frequently asked
What is the Remix route?
The Remix route is for clients who do not yet have an Infobip account. You register on client.arino.one, confirm your account by OTP and email, and then follow Infobip's own signup flow to create and pay for an Infobip account that you own directly. Arino is the platform; Infobip bills you for messages.
What is the BYO route?
The BYO (Bring Your Own) route is for clients who already have an Infobip account. You register on client.arino.one, confirm your account, and then connect your existing Infobip keys. You continue to pay Infobip directly for usage.
What is the difference between Self-build and We build it for you?
Self-build is free: you click the Lovable remix link and customize the Arino One template yourself. We build it for you is a one-time $350 fee for Arino to set up the instance on your behalf. Either way, the resulting instance is yours and you own your own Infobip account.
Is the $50/month Arino Core connection required?
No. The $50/month connection is optional after your instance is built. Pay it to stay connected to Arino for WebRTC calling at $0.009/minute, support, management, and updates. Skip it and keep the instance without an Arino connection or support.
What does the $350 setup fee cover?
The $350 one-time fee covers Arino setting up the instance for you under the We build it for you option. It does not include Infobip usage, Meta fees, or the optional $50/month Arino Core connection. See billing-and-plans for the full rate card.
Can I switch routes or options later?
Yes. If you start without an Infobip account you can bring your own later. If you self-build you can later ask Arino to take over management by adding the $50/month connection. If we built the instance for you you can still self-build or fork the template at any time.
Does my route affect data residency or architecture?
No. Every Arino One instance uses the same dedicated console, isolated database, and regional storage model described in architecture-and-regions. Your route and build option determine who creates the Infobip account and who builds the console, not where data lives.
Apply this to your own deployment
This guide describes decisions we make on live instances. Tell us your channels, systems and region and we will map it to an architecture outline, a provisioning plan and an indicative commercial model — usually within one business day.