Content in your ERP, a site with no limits
Pages, posts, services, team, projects or events: you define them in the ERP, with your own fields, and they show up on any site. We build the site on your brand, or your team connects it, in whatever technology you prefer.
Read on the blogIn plain words: what headless means and when it pays offSmile with confidence
Book a consult in seconds at open slots only, with instant email confirmation.
- ✓Open slots only
- ✓Email reminder
- ✓Instant confirmation
Not just pages and posts: you choose the types
Create the types your site needs: rooms, projects, courses, doctors, properties, recipes. Each with its own fields: text, images from the gallery, prices, dates, lists or links to other entries.
Fields are checked on save, and changing the structure does not break older pages. For the team building the site, the structure also comes as TypeScript types.
- Your own types and fields, per site
- Categories, tags and links between entries
- Images from the company gallery
- TypeScript types generated from your structure
# All rooms, with their fields GET /api/site/v1/entries/rooms { "title": "Pine Room", "fields": { "price_per_night": 95, "guests": 2, "gallery": [ … ], "amenities": ["sauna", "terrace"] } }
Drafts, preview and scheduled publishing
Write in the editor, see the page on the real site before you publish, and schedule a post for Monday morning. Autosave protects you from lost text, and earlier versions stay in the history.
When you publish, the site gets a signal and updates itself. No waiting on a developer for a comma.
- Preview on the real site
- Scheduled publishing
- Version history
- The site updates on publish
| Page | Path | Type |
|---|---|---|
| Terms and conditions | /p/terms | Legal |
| Return policy | /p/returns | Legal |
| Shipping and payment | /p/shipping | Page |
| About us | /p/about | Page |
The same site, in your clients’ languages
Pick the site’s languages, and each entry is translated in its own record, with a title, URL and SEO text per language. Fields that stay the same across languages, like price or photos, are shared.
The site asks for content in the visitor’s language and gets the translation, or the base language where a translation is still missing.
- Languages chosen per site
- URL and SEO per language
- Shared fields, translated only where needed
# The same page, in Romanian GET /api/site/v1/entries/rooms/pine-room ?locale=ro { "title": "Camera Brad", "slug": "camera-brad", "seo": { "title": "Camera Brad, saună și terasă" } }
Menus, redirects and SEO, all from the ERP
The header and footer menus are edited in the ERP. So are redirects from old URLs, titles and descriptions for Google, and the sitemap.
Site search comes from the ERP too, so visitors find rooms, posts and services in one place.
- Multi-level menus
- Redirects, so you keep your search rankings
- Sitemap built from published content
- Search across all site content
Book a consult online at open slots. Implants, orthodontics, and hygiene with experienced clinicians.
- ✓Title and description on every page
- ✓Structured data for Google
- ✓Sitemap and robots.txt
- ✓Redirects from old URLs
- ✓Images with alt text
- ✓Clean heading structure
Forms land in your ERP and CRM
Contact and quote forms are defined in the ERP and saved there, with everything the person filled in. They are emailed from your company address and, if you use the CRM, arrive as leads with their source.
The same site can have online booking, a jobs page and client accounts, all tied to the ERP.
- Requests saved in the ERP, emailed to your team
- Leads in the CRM, with source and campaign
- Bookings, jobs and reviews on the same site
- Client accounts with bookings and data
All your company’s sites, from one place
Each site has its own structure, content, languages and domains. A group with several brands, a network of clinics or an agency running client sites all work from one ERP.
Your team only sees the sites they have access to, and each site gets its own separate access.
- Separate structure per site
- Per-user permissions
- Separate access for each site
Works with any kind of site
Astro and Next.js
Our demo sites are built this way: pre-rendered pages, very fast.
Any framework
Nuxt, SvelteKit, Remix or plain HTML. The API speaks JSON.
Documentation
Your content types appear in the docs, with their fields.
In your app too
The same content can show up in your company’s mobile app.
The same backend, for everything else
Headless 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 worksRIVIL Headless
One backend for everything you build.
See how it worksWhat people ask us
Do I have to use a site you build?
No. We can build it on your brand, or your team builds it on the API. The content stays in the ERP either way.
I have a WordPress site. What happens to it?
We can keep it and connect its forms to the CRM, or rebuild it on RIVIL and move the content worth keeping, with redirects from the old URLs.
Who can edit the content?
Anyone on your team you give access to, using the ERP’s users and roles. No separate site account needed.
Can I have multiple languages?
Yes. You choose the languages per site, and each entry has its own translation, with a URL and SEO per language.
How fast does a change show up on the site?
On publish, the site gets a signal and refreshes its pages, so the change shows up right away.
Does it work for a small site of a few pages?
Yes. Start with a few pages and a form, and the structure grows with your business.
Want a site you edit from your ERP?
We will show you how your site’s content would look in the ERP and how it ties into forms, bookings and the CRM.