How Vivetra’s Shared-Core Platform Works

Every Vivetra service — Vet Practice, Hospital, Boarding, Shelter, Equine, Livestock — runs on the same foundation underneath, called shared-core. When you sign up, you’re not choosing one product out of six unrelated systems; you’re choosing which service (or services) sit on top of a single platform that already handles patient records, staff accounts, scheduling, and billing. That one decision is what makes everything below possible.

One deployment, one practice

When you sign up, your practice gets its own deployment — not a shared seat in one large multi-tenant database with every other Vivetra customer’s records sitting in neighboring rows. Your data lives in its own dedicated space, and it is never commingled with another practice’s data.

What you never do is any of the operational work that isolation would normally require — that’s the next part.

Fully managed hosting — nobody on your staff touches a server

Your deployment runs on infrastructure that is entirely our responsibility, not yours. Nobody on your staff owns a machine, patches it, backs it up, or gets a call when it goes down. It is fully managed for you: you never touch a server, never patch an operating system, and never restore your own backup.

Right now, shared-core plus your first service runs $200/month — unlimited doctors and staff, managed hosting included in that price, not a footnote you find later. See the full pricing breakdown for every service combination.

Add a service later without losing anything

Say you start with Vet Practice on day one, and eighteen months later your practice takes on a boarding wing. You don’t buy a second product, migrate any data, or ask your team to learn a second login. Adding Boarding plugs into the same deployment you already have — the same patient records, the same staff accounts — with no export/import step, no downtime, and nothing that already existed is touched.

It adds one flat amount to the same monthly bill: right now that’s $50/month per additional service, for as many of the six as your practice needs — unlimited staff and managed hosting stay included at every step.

One chart, not two systems stitched together

Here’s what shared-core looks like on an actual day, not as a diagram. A dog named Biscuit has surgery through your Vet Practice service — the surgeon’s post-op orders (medications, dosages, a monitoring schedule) go on the record the same way they always do. If your practice also runs the Boarding service and Biscuit’s owner books a recovery stay, the kennel tech doesn’t retype those orders into a separate boarding system, and nobody prints an aftercare sheet to hand-carry between departments.

The kennel tech opens the exact same chart — the same medication orders, the same treatment log, the same vitals — and checks off each dose and each vitals check right there. When your vet reviews Biscuit’s stay afterward, it reads as one continuous record: surgery, then recovery, then discharge, not two half-histories somebody has to reconcile by hand. That’s what “shared core” means in practice: it’s one patient chart that two services both read and write to, because they’re built on the exact same platform underneath — not a slogan, a structural fact you can go check.

Run Boarding on its own, without Vet Practice on the same deployment? The same chart still exists for a genuine medical-aftercare stay — it’s fed by your client’s outside surgeon’s written discharge instructions, transcribed in and attached as the source document, instead of an in-house order.

Installs like an app, updates like a website

Your team doesn’t install Vivetra from an app store, and there’s no IT project to set it up on every workstation. Open Vivetra in a browser once, and the browser offers to install it — an icon on the desktop or home screen, its own window, no address bar, indistinguishable at a glance from a native app. Under the hood, that’s a Progressive Web App (PWA), and it’s also what decides how updates work.

New releases download in the background the moment they’re ready — no waiting, no manual check, no version number to track. Turning a downloaded release on is scheduled for your practice’s quiet hours, and even then, Vivetra never interrupts a chart someone is actively working in: if there’s unsaved work open, the update waits until it’s done. You don’t get a “restart to update” interruption in the middle of an exam.

For barn calls and farm visits — the Equine and Livestock services — a handful of field-record screens keep working even when a signal drops, queuing entries to sync the moment you’re back online. Everywhere else, Vivetra expects a normal connection, the same as any web app.

Questions about how this works

See it priced out for your practice

The architecture is the same no matter which services you pick or how many countries’ worth of practices you compare it to — one deployment, fully managed, add services whenever you’re ready.

Get Started See full pricing