Everything from one place

One system, not hundreds

Most companies run their website somewhere else, their shop somewhere else again, and their ticket system at a third provider. That means three logins, three invoices, three contacts — and the data sits in three places. We build all of it on the same core, and what it produces goes into your platform.

One platform, three ways in At the top sits the RIVUS360 platform with all its modules. Below it, separated by a firewall in the edge zone, sit three groups: websites built on our site core, shops with their variants, and single modules such as signatures, tickets, remote support and a customer login. Everything these produce goes into the platform over an API on the private network. RIVUS360 the platform — every module, one login internal zone · no route from the internet API over the private network edge zone (DMZ) — reachable from the internet Websites on our site core Chat Newsletter Contact requests Content, in several languages existing sites can be rebuilt Shops selling, renting, booking Online shop Services to order Rental Appointments and booking orders land in the platform Single modules for people outside Signing PDFs Ticket support Remote support Help pages Customer login no account in the main system needed

What that means in practice

Websites

Your public website runs on our site core. Chat, newsletter and the contact form are not plugins but parts of it. A contact request does not land in a mailbox that someone has to copy from — it arrives in the platform as a lead, with its source and its history.

An existing site can be rebuilt on the core. The content moves across; the design stays yours if you want it to.

Shops

Selling, renting, booking appointments, or a service that is quoted individually — these are four different processes, and they are built as such. An order becomes a customer, an invoice and, if you want, a contract, without anyone retyping it.

Stock, articles and prices come from the same place that your internal system uses. There is no nightly sync that can fail.

Single modules

Some things are meant for people who are not your staff: a customer who signs a PDF, a supplier who reports a fault, a technician who needs remote support, a freelancer who records hours. They get exactly that one page — and no account in your main system.

These pages sit in the edge zone, separated by a firewall. What they collect goes into the platform; the way back does not exist.

A record, not a form

In most systems a customer is a row with a phone number on it. Here a customer is a file, and everything that happens with that customer hangs on it — without anyone having to file it there.

A customer record

Master data, addresses with coordinates, e-mail addresses, phone numbers, bank details, tax information, relationships to other people and companies.

And next to it, as its own tabs:

  • Appointments
  • Reminders
  • Correspondence
  • Notes
  • Files
  • Websites
  • Recruiting
  • History

A project

Steps that depend on each other, each with its own sub-items — one example here carries six steps and fourteen elements below them.

And hanging on the same project:

  • People involved, staff and customers
  • Tasks out of every step
  • Comments
  • Attachments
  • Links to recruiting projects
  • Links to any other record
  • History

A task

Sub-tasks with their own progress, priority, category, due date — and the project it came from.

Straight from the task you create:

  • An appointment in the calendar
  • A reminder that has to be accepted
  • Comments
  • Links
  • History

That is the difference the word integration is usually asked to carry. Nobody copies an address into the appointment, nobody files the mail under the customer, nobody keeps a second list of who is on the project. It is the same record — so it is right everywhere at once, or wrong everywhere at once.

Why this usually costs less

The modules already exist

An agency writes a shop for every customer. We have one and configure it. What is left to build is what makes your case different — and that is a fraction of the whole.

No plugin ceiling

A system assembled from plugins can only do what its plugins do. When a requirement does not fit, the answer is "not possible" or a second plugin that half fits. We have the source, so the answer is a price and a date.

One contact for all of it

Operation, updates and further development come from the same place as the build. Nobody has to find out whose fault something is before it can be fixed.

Tell us what you have today

A website, a shop, a ticket system — whatever is already running. We will tell you what can move onto the core, what stays as it is, and what that costs.

Help & Support

Looking for something else? Our applications and the documentation are one click away.