One backend for anything you build
A marketing site, an online store, a mobile app or a whole platform: they can all work with the same ERP. Clients, products, orders, appointments and content live in one place, and we build the part people see the way you want it.
Read on the blogIn plain words: what headless means and when it pays off
- Clients and accounts
- Products and stock
- Orders and invoices
- Appointments
- Content and menus
- Payments
Any screen your clients or your team look at
The ERP holds the data and the rules. On top of it we build exactly the interface you need, in the right technology for it.
Data in one place, the interface anywhere
In a classic platform, the part your clients see and the part you work in are glued together. The design is whatever the template allows, and any big change means a migration.
With RIVIL, the ERP holds clients, products, stock, orders and content, and your site, store or app reads and writes them through an API. You can have three completely different interfaces working with the same clients and the same stock.
- Free design, no template limits
- The same data on every channel
- Change the frontend without moving data
- Each channel only reaches what it needs
# The same client, seen from any channel GET /api/v1/clients/c_2841 { "name": "Anna Miller", "orders": 6, // from the store "appointments": 3, // from the app "invoices": 9, // from the ERP "source": "site / google" }
Site, store, app and platform, on the same data
The site takes its pages and posts from the ERP, the store sells from the same stock, the mobile app books into the same calendar, and the portal shows clients the invoices issued in the ERP.
When a client buys in the store and then books from the app, you see them once, with their full history.
- Content, menus and SEO for the site
- Catalog, cart, checkout and payments for the store
- Client account, bookings and orders in the app
- Portals and platforms with your users and rules
- Clients and accounts
- Products and stock
- Orders and invoices
- Appointments
- Content and menus
- Payments
If something is missing, we build it
The platform is made of modules. If your app needs data or rules that do not exist yet, we add a new ERP module with your fields and flows.
The new module shows up in the API on its own, with reads, writes and events, so the frontend can use it from day one. You get one platform, not one more system to maintain.
- New modules, fields and flows for your needs
- Added to the API and docs automatically
- Users, roles and permissions from day one
- Connected to the systems you already use
| Number | Client | Equipment | Technician | Status |
|---|---|---|---|---|
| #2041 | Alfa Construct | Generator 20 kVA | Radu M. | In progress |
| #2040 | Beta Services | Pump CR-5 | Dan A. | Waiting for parts |
| #2039 | Gama Trade | Compressor 7 bar | Radu M. | Done |
| #2038 | Delta Med | Autoclave | Ioana D. | Delivered |
An AI agent can work with the same data
Besides the API, the platform also talks to AI agents. An assistant can look up a client, check stock or prepare a quote, with the permissions you give it.
Anything that changes data stays a proposal until a person approves it, and sensitive data stays out of its reach.
- Permission-based access for AI agents
- Proposals approved by a person
- The same activity log as everything else
A complete API, not a handful of endpoints
Anything you do in the ERP can be done through the API: read, create, update and trigger actions, from issuing an invoice to confirming an appointment. Every change sends an event, so your site or app knows right away.
- Read and write across all modules
- Actions: issue, send, approve, confirm
- Signed webhooks on every change
- OpenAPI documentation, always current
# Create an appointment from any app POST /api/v1/appointments client, service, specialist, time # Issue the order's invoice POST /api/v1/invoices/{id}/issue # Know right away what changed webhook appointments.created webhook invoices.issued
The hard part is already done
We do not rebuild what already exists in the ERP. We only build what makes your app different.
Clients and accounts
Client records, email and password accounts, GDPR consent.
Money
Invoices, card payments, collections and reports.
Operations
Appointments, stock, orders, shipping, projects and tasks.
Messaging
Emails and texts to clients, from the same data.
Pick where you start
Headless website
Content in ERP, a site with no template limits, in any language.
See how it worksHeadless ecommerce
Catalog, cart, checkout and accounts, on any frontend.
See how it worksMobile apps
iOS and Android apps for your clients or your field team.
See how it worksPlatforms
Portals, marketplaces and internal apps on the same data.
See how it worksWhat people ask us
What does "headless" actually mean?
That the ERP does not dictate how your site or app looks. Data and rules live in the ERP, and the interface is built separately and talks to it through an API. You can change the design any time without moving data.
Do you build the frontend, or does my team?
Either. We can build it, from design to launch, or your team builds it on the API, with the docs and our help.
Which technologies do you use?
We pick per project. For sites and stores, usually Astro or Next.js. For mobile apps, React Native, Flutter or native. The API speaks JSON, so it works with anything.
Do I have to use the whole ERP?
No. You start with the modules your app needs and add the rest as you grow.
What if I need something the ERP does not have?
We build it as a new module. It shows up in the API with reads, writes and events, like the rest of the platform.
Can I connect the apps I already use?
Yes, through the API and webhooks. Data can flow both ways, without anyone copying it by hand.
Have an idea for a site, store or app?
Tell us what you want to build. We will tell you how it would connect to the ERP, what already exists and what needs building.