Remix the Arino One template
The Arino One remix template is a production front end — marketing site, docs and console shell — that you fork in Lovable, rebrand as your own, and connect to an Arino One instance instead of building a messaging surface from scratch. Remixing is simply Option 1: Self-build, the free build option, and it is available on both onboarding routes.
Where remixing fits
Onboarding is two questions. First the route: Remix if you do not yet have an Infobip account and will create one, or BYO if you already have one to connect. Then the build option:
| Option | Who builds it | Cost |
|---|---|---|
| Option 1 — Self-build | You, from this template, in your own Lovable workspace | Free |
| Option 2 — We build it for you | Arino sets the instance up for you | Flat $350 one-time |
Remixing is Option 1 and nothing more: it is a way of building the instance, not a separate product tier. Whichever route and option you pick, you own your own Infobip account and pay Infobip and Meta directly for usage — Arino is never in the middle of your messaging bill.
After the instance is live, the $50/month Arino Core connection is optional. Take it for WebRTC in-browser calling at $0.009/minute, support, management and updates; skip it and keep the instance running independently with no recurring Arino fee. Self-building now does not lock you out of that connection later.
What you get
Remixing gives you a complete Lovable project, not a hosted widget: the marketing pages and navigation shell, a content-driven docs system identical in structure to this one, an authenticated console with inbox, contacts (CDP) and campaign views, and front-end code already wired to call an Arino One instance's API for messaging, contacts and automations. Because it is a fork, the code lives in your own Lovable workspace — you decide on hosting, domain, deployment cadence and any custom features you add on top.
What the template does not include is a back end. The remix is a front end only; it still needs an Arino One instance behind it to send and receive messages, store contacts and run automations. Connecting the two is covered in connect the template to your instance.
When to self-build
Self-build when brand ownership of the front end matters — your own design system, your own domain, the ability to add custom screens — and you are comfortable maintaining that front end in Lovable. It also suits teams who want a working head-start rather than building a console from a blank project, and teams who want no Arino build fee at all.
Choose We build it for you instead when you want the fastest path to a running instance and would rather not do the build work. The underlying capabilities — channels, automations, CDP and campaigns — are identical either way. The decision is about who does the build and who maintains the interface, not about feature access.
Getting started
Once you have decided to self-build, the next steps are rebranding the fork (tokens, logo, copy, legal pages) and connecting it to your instance. Those two tasks are independent — rebrand first and connect later, or connect a lightly modified template first and refine the brand afterwards.
Frequently asked
What exactly do I get when I remix the template?
A complete Lovable project: marketing pages, a docs system, an authenticated console shell with inbox, contacts and campaign views, and the front-end code that talks to an Arino One instance's API. You get the source, not just a hosted page, so you can rebrand and extend it freely.
Is self-building free?
Yes. Self-build is Option 1 and costs nothing from Arino — you fork the template into your own Lovable workspace and build it yourself. You pay Lovable directly for hosting if your plan requires it, and Infobip and Meta directly for usage.
Do I need to know how to code to remix the template?
Basic comfort editing a Lovable project helps, but most rebranding is changing design tokens, copy and images rather than writing logic. Anything beyond that — new features, custom logic — is regular Lovable development.
Does remixing depend on which onboarding route I'm on?
No. Self-build is available on both routes. On the Remix route you create your own Infobip account first; on the BYO route you connect the Infobip account you already have. Either way the remixed front end works the same.
Can Arino manage my remixed instance later?
Yes. After your instance is built you can add the optional $50/month Arino Core connection for WebRTC in-browser calling at $0.009/minute, support, management and updates. Nothing about your design or codebase needs to change.
What if I don't want to build the front end myself?
Choose Option 2 instead: We build it for you at a flat $350 one-time fee. You still own the resulting instance and your own Infobip account.
Who owns the code once I remix it?
You do. Remixing forks the project into your own Lovable workspace, so you control hosting, deployment and further changes independently of Arino.
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.