Last fact-check: August 9, 2026.

Vetspire is a cloud-based veterinary practice information management system (PIMS) that combines medical records, scheduling, billing, inventory, client communication, reporting, automation, and optional AI and specialty workflows. Its current public material is detailed enough to build a serious evaluation, but not enough to calculate the final price of a real deployment.

This independent desk review uses Vetspire's current website, subscription agreement, user manual, support center, and developer documentation. We did not receive a demo, use a live clinic account, migrate records, interview customers, or accept payment from Vetspire. We therefore do not assign a star rating, repeat vendor testimonials as independent evidence, or claim that a feature will produce a particular clinical or financial result.

Vetspire Review: The Short Verdict

Vetspire deserves a shortlist for U.S. veterinary practices that want a modern cloud PIMS, especially when real-time medical-record collaboration, multi-location controls, a documented GraphQL API, workflow automation, and optional AI or specialty modules matter. The public product scope covers much more than basic appointment and invoice functions, and the first-party manual gives buyers useful material for a technical proof of concept.

Its strongest documented points are:

  • encounter-centered medical records with simultaneous multi-user editing;
  • scheduling, reminders, inventory, invoicing, payments, dashboards, and financial reporting;
  • two-way messaging, newsletters, online booking, mobile access, macros, and automated triggers;
  • configurable roles, organization settings, location pricing, and audit-oriented reports;
  • a public GraphQL schema with production, staging, and sandbox endpoints;
  • a broad first-party integration catalog covering labs, imaging, inventory, communications, pharmacies, insurance, SSO, and dictation;
  • three implementation tiers with training and rollout options;
  • contractual encryption, access-control, vulnerability-management, and secure-development commitments;
  • a 99.9% monthly availability commitment in the published subscription agreement.

The main buying risks are also concrete:

  • the current pricing link returns 404 and no current public dollar amount was available in the first-party material reviewed;
  • subscription fees are charged per doctor, while implementation, migration, usage, API certification, and third-party integration costs may be additional;
  • the initial term and exact commercial scope live in the order form, not the marketing pages;
  • billing can start no later than 12 weeks after the effective date even if the customer has not begun using the service;
  • implementation rescheduling after a permitted change can trigger published fees;
  • the public feature page calls several capabilities “add-ons,” so inclusion must be confirmed line by line;
  • data migration may be incomplete, and the agreement places conversion risk on the customer;
  • the API key is powerful enough to read and write an organization's data and needs administrator-grade controls;
  • critical support targets and service credits require understanding the contract's definitions and notice process;
  • after termination, the contractual data-retrieval window is only 30 days and transfer assistance may cost extra.

The practical verdict is conditional: Vetspire can be a strong fit, but only after a clinic validates its highest-risk workflows with its own data, receives a complete three-year cost schedule, and negotiates acceptance, export, security, and support terms in writing.

What Is Vetspire?

Vetspire describes itself as an AI-enabled, cloud-based veterinary PIMS. The current all-features page lists medical records, scheduler, automated reminders, inventory management, financial reporting, internal chat, user tasks, payment processing, macros, client pricing, two-way messaging, newsletters, admin triggers, a mobile app, and online booking.

The platform is aimed at more than one clinic type. Vetspire's solutions overview identifies general practices, enterprise groups, emergency hospitals, specialty clinics, mobile clinics, and universities. That breadth does not mean every configuration works equally well for every buyer. A two-doctor general practice and a 50-location group should run different proof-of-concept scripts, require different controls, and expect different implementation work.

Several specialized capabilities are presented separately from the core list:

  • an AI Suite with Scribe and Summary;
  • WINK for ophthalmology, SMILE for dentistry, and HOOF for equine use;
  • boarding management;
  • wellness plans;
  • NOVA electronic treatment sheets and whiteboard workflows.

The public page labels these as add-ons, even while using broad language about avoiding extra development costs. The subscription agreement says selected services, fees, implementation tier, migration, and other functionality are specified by the order form and pricing sheet. The safe interpretation is that a buyer must ask whether each module is included, optional, usage-priced, or subject to a separate vendor agreement.

Is Vetspire legitimate?

Yes in the ordinary vendor-verification sense: the current site identifies Vetspire, LLC; publishes a named leadership team, a subscription agreement, a privacy notice, a support center, a detailed product manual, and a public developer API; and provides a business address and legal notice contact. Those signals establish a real operating software vendor, not that the product is automatically right for a particular practice.

Searches for “Thrive Vetspire” or “Vetspire Pathway” can reflect a clinic network, historical deployment, login route, or other commercial relationship. The current first-party pages reviewed identify the contracting product company as Vetspire, LLC and do not state that Thrive Pet Healthcare owns Vetspire. That is an inference from the current public record, not an ownership opinion. If ownership, financial backing, or a change-of-control clause matters to procurement, request the current corporate structure and contracting entity directly rather than relying on a search snippet.

Medical Records and Clinical Workflow

Vetspire's medical-records page describes the patient chart as an encounter-centered record that supports real-time, multi-user editing, configurable input types, filtering, and sharing. It connects histories with scheduling, billing, inventory, lab results, medications, tasks, reminders, communications, and other operational data.

Those capabilities are promising for a busy hospital, but a marketing description cannot show whether the interface fits actual care. A useful demo should include:

  • a wellness encounter and a complex sick visit;
  • concurrent doctor and technician edits to the same encounter;
  • a corrected note after signature or locking;
  • a medication with weight-based instructions and a refill;
  • an external lab order, result, amended result, and failed interface;
  • uploaded images and a large outside record;
  • client and referring-veterinarian sharing;
  • duplicate clients, co-owners, deceased patients, and record merges;
  • a treatment estimate that changes before invoicing;
  • a controlled-drug workflow appropriate to the clinic's jurisdiction;
  • a complete audit trail for who viewed or changed material information.

The manual documents configurable user roles and a transition toward more granular permissions. That can support least privilege, but only if the practice maps real job functions to roles, removes access promptly, and tests negative permissions. Ask a receptionist, technician, associate veterinarian, relief veterinarian, inventory manager, finance user, and external IT support user to complete their normal tasks in the test environment.

Vetspire's agreement explicitly says the software does not replace independent veterinary judgment and that AI-generated material is fallible. That is the right baseline. A clinic should define who may use generated notes, what must be reviewed, how corrections are attributed, whether recordings are retained, and which data may be used by AI-related services before enabling them.

Scheduling, Communications, Billing, and Inventory

The core feature set reaches across the front desk and business office. The product pages describe real-time scheduling, reminders, online booking, two-way messages, campaigns, patient-facing mobile access, payments, client pricing, inventory usage reports, and financial dashboards.

For scheduling, reproduce the constraints that usually break generic demos:

  • provider, location, department, room, and equipment availability;
  • appointment-type duration and species restrictions;
  • double-booking and emergency-slot rules;
  • multi-pet households and linked appointments;
  • boarding or inpatient handoffs;
  • cancellations, no-shows, late arrivals, and rescheduling;
  • online requests that need clinical triage rather than automatic booking;
  • operation during an internet or third-party messaging outage.

For client communication, test consent, quiet hours, shared phone numbers, wrong numbers, language preference, opt-out, delivery failures, attachments, and sensitive content. Exhibit C of the subscription agreement places responsibility for applicable messaging rules, consent, unsubscribe handling, and calling-time restrictions on the customer. Automation should be approved by the clinic's compliance lead or counsel, not switched on merely because a template exists.

For billing and inventory, reconcile a full day's activity against the existing system. Include deposits, partial payments, refunds, chargebacks, taxes, discounts, packages, wellness-plan activity, declined cards, unpaid invoices, controlled inventory, lot numbers, expired items, purchase orders, multi-location transfers, and end-of-day reporting. A dashboard that looks useful is not sufficient if the accounting export or payment settlement does not reconcile.

The official integrations catalog includes Vetcove and Inventory Ally for purchasing or inventory workflows, multiple diagnostic and imaging systems, communication providers, online pharmacies, insurance connections, and other services. Inclusion in the catalog proves documented connectivity, not that every direction, field, version, or support path is included in the quote.

Vetspire AI: Useful Scope, Necessary Controls

Vetspire markets AI Scribe and Summary as embedded tools and makes time-saving claims on its public site. Those figures are vendor claims, not independent results from this review. The contract is more important for risk: it says AI services are fallible, the customer must validate their output, and Vetspire does not warrant AI-generated material.

A safe pilot should measure, rather than assume:

  • note completion time before and after the tool;
  • correction rate by section and encounter type;
  • missed negatives, laterality, dose, duration, and diagnostic qualifiers;
  • speaker attribution in noisy or multi-patient settings;
  • performance with accents, abbreviations, species, and specialty terminology;
  • whether a clinician can see the source recording or transcript;
  • how edits and final approval appear in the audit trail;
  • recording consent, retention, deletion, subprocessor, and training-data rules;
  • what happens when connectivity fails or the generated text is unavailable.

Do not copy an AI note into the medical record without an accountable clinician reviewing it. Establish a policy for high-risk content, prohibited uses, client disclosure where required, and incident escalation. Ask whether AI access and usage limits differ between Standard, Pro, enterprise, or add-on terms, because public feature visibility is not a contractual entitlement.

Vetspire Pricing in 2026

No reliable current public dollar price was available from Vetspire during this fact-check. The site's pricing link led to a 404 page on August 9, 2026. A third-party figure, an old quote, or another clinic's invoice is therefore not a substitute for the current order form.

The published subscription agreement does reveal how the commercial model works:

  • monthly subscription fees are charged per doctor;
  • a doctor working fewer than ten shifts in a calendar month is excluded from that doctor count under the standard wording;
  • certain functionality, including texting and faxing examples, can incur per-use fees;
  • every customer must select an implementation-services tier;
  • migration or conversion from a legacy PIMS is optional and must appear on the order;
  • other functionality may use then-current pricing;
  • API certification, a Vetspire API integration, or a third-party integration can carry fees;
  • taxes and certain payment-vendor arrangements can add to total cost.

This makes a single “price per month” comparison misleading. Build a three-year total-cost model with these rows:

  1. subscription price for every billable doctor and location;
  2. treatment of relief, part-time, rotating, and inactive doctors;
  3. Standard, Pro, enterprise, specialty, AI, boarding, wellness, and NOVA modules;
  4. implementation package and every included training session;
  5. data assessment, conversion, validation, and remediation;
  6. SMS, fax, storage, payment, terminal, and other usage charges;
  7. laboratory, imaging, pharmacy, inventory, SSO, and other integrations;
  8. API access, certification, support, and rate-limit overages;
  9. travel or on-site rollout expenses;
  10. price increases, taxes, renewal, and exit assistance.

Request a worked sample invoice for a low, typical, and peak month. Define a billable doctor with examples. Ask what happens when a new doctor starts midmonth, a relief doctor crosses ten shifts, a doctor works at several locations, or a provider is deactivated late.

Contract and cancellation terms

The initial service term is whatever the order form says. Under the standard September 3, 2025 agreement, the contract then renews month to month unless either party gives written notice at least 30 days before the current term ends. Fees for the remaining current monthly term remain due.

Billing begins at the earlier of completed implementation and migration, or 12 weeks after the effective date. The agreement says fees are non-refundable and non-cancellable even if the customer does not start using the service or requests early termination. That creates a procurement deadline: the customer needs resources, data, integration owners, and acceptance criteria ready before signing.

Implementation fees are due before implementation begins. The agreement permits one good-faith implementation-date extension, except for Great Dane, and then lists $1,000 for a later date change on other service levels and $5,000 for a Great Dane date change. Ask the order to define what counts as a change, which party caused it, and what happens when a legacy vendor, interface partner, or Vetspire dependency delays go-live.

At termination, Vetspire promises to make customer data available electronically for 30 days while subscription fees continue. Transfer assistance can be billed at then-current rates. After that window, Vetspire may delete the data. Negotiate the export format, attachments, audit history, schema, delivery method, validation, cost, and deletion confirmation before implementation—not during cancellation.

Implementation and Data Migration

Vetspire's implementation page presents three tiers:

  • Maltese, positioned for tech-savvy clinics with simpler workflows;
  • Labrador, positioned for teams that want more optimization;
  • Great Dane, positioned for scaling clinics that need fuller configuration and rollout support.

The comparison names virtual training, workflow case studies, go-live support, personalized onboarding, custom setup, business and reporting training, additional sessions, on-site rollout, and enterprise setup. The page's accessible table does not clearly expose every checkmark, so do not infer which item belongs to which tier. Require a signed matrix with hours, attendees, format, travel, recordings, deliverables, and completion criteria.

The agreement is more cautious than the marketing page: Vetspire will first assess the legacy PIMS, may determine that it cannot migrate the data, and says conversion may be limited or leave some information inaccessible. The customer accepts the migration risk under the standard terms.

Protect the practice with a staged acceptance plan:

  1. inventory all source systems, interfaces, archives, and local files;
  2. define the record types and date ranges to migrate;
  3. receive a written field map and excluded-data list;
  4. retain a practice-controlled backup of the source;
  5. migrate a representative sample first;
  6. validate totals and high-risk clinical records independently;
  7. test every required integration in staging;
  8. rehearse downtime, rollback, and cutover reconciliation;
  9. obtain clinician, operations, finance, and privacy sign-off;
  10. preserve the legacy read-only system until acceptance is complete.

Use records with long histories, attachments, images, aliases, merged patients, deceased patients, co-owners, estimates, credits, open balances, inventory lots, reminders, and communications. Count records and attachments before and after. Visual spot checks alone will not find systemic omissions.

For rollout hardware and intake-device planning, our veterinary intake and kennel supplies guide covers physical workflow categories; it does not replace Vetspire's current compatibility requirements or the clinic's infection-control, privacy, and accessibility review.

Vetspire API Documentation and Integrations

Vetspire has an unusually visible public GraphQL API reference. It publishes production, staging, and sandbox endpoints and documents queries and mutations across clients, patients, appointments, medical records, billing, inventory, treatments, and communications. The API currently enforces a maximum GraphQL query depth of eight.

That is a meaningful advantage for a buyer that needs controlled interoperability. It is not a promise that every schema object is licensed, stable, supported for a particular workflow, or safe to expose. Feature flags and schema types can exist even when a capability is not enabled for the customer.

The most important security warning comes from Vetspire itself: a secret API key can provide read and write access to the entire organization's data and should be treated like an administrator password. All calls must use HTTPS. The user manual adds that keys expire after four years by default, can be assigned a role, and create an associated API-user profile; deleting the key does not delete that profile.

For every integration:

  • create a unique role and key with the minimum required permissions;
  • use separate sandbox, staging, and production credentials;
  • store secrets in an approved vault, never source code or a shared document;
  • log purpose, owner, vendor, creation, expiration, and last use;
  • rotate credentials on a shorter clinic-defined schedule;
  • monitor read and write activity and failed calls;
  • test pagination, idempotency, retries, rate limits, and partial failure;
  • define conflict ownership when two systems update one field;
  • revoke the key and deactivate its API user at termination;
  • document export behavior without relying on a custom integration.

The subscription agreement also says third-party API access requires Vetspire's prior written approval and an executed API agreement, and that API certification or integration may have a fee. Include this approval and cost in the project plan before committing to an outside developer.

Integration coverage to verify

The first-party manual lists integrations across:

  • IDEXX, Antech/Heska, Zoetis, VitalPACS, Vet Rocket, SignalPET, and other diagnostic or imaging tools;
  • Inventory Ally, Cubex, and Vetcove;
  • Twilio, RingCentral, AllyDVM, Documo, Dialpad, and other communication services;
  • Vetsource, Trupanion, Covetrus vRxPro, HomeAgain, TeleTails, PetLink, and AKC Reunite;
  • Microsoft 365, Okta, and OneLogin SSO;
  • Dragon Veterinary, Talkatoo, and Talkingvet dictation paths.

Ask for the exact product, version, direction, field map, frequency, queue visibility, duplicate behavior, separate agreement, support owner, and fee. A documented integration may depend on the third party, and the standard agreement places responsibility for third-party security issues on the customer in some circumstances.

Security, Privacy, and Availability

Vetspire's current legal terms contain useful security commitments. The data-security attachment describes least-privilege access, unique credentials, administrative-account controls, account audits, vulnerability scanning, periodic external penetration testing, segmentation, encryption of personal information in transit and at rest, secure development practices, patching, web application firewalls, and personnel screening and training.

The user manual documents configurable complex-password requirements, automatic session timeout, SSO with Microsoft 365, Okta, and OneLogin, and granular user roles. These are positive controls, but public documentation is not an assurance report. Ask for current independent evidence, scope, exceptions, remediation, hosting regions, subprocessor list, cyber-insurance limits, incident-notification timeline, backup design, restore-test results, recovery objectives, and vulnerability-disclosure process.

Vetspire's medical-record page uses the phrase “HIPAA-inspired security protocols.” Veterinary patient records are not automatically governed by human-health HIPAA rules, while client personal information, payment information, state privacy law, professional rules, and contractual obligations can still apply. Do not convert that marketing phrase into a claim of universal legal compliance. Map the practice's actual jurisdictions, data types, and duties with qualified counsel.

The subscription agreement says the customer owns customer data. It also permits Vetspire to use customer data to provide and monitor the service and to use de-identified customer data for service improvement, veterinary or pharmaceutical research, and AI research and development. Buyers should review the definition and process for de-identification, permitted recipients, retention, re-identification controls, opt-out or negotiated restrictions, and treatment of derived data.

Reliability and support

Exhibit A states 99.9% monthly availability, excluding scheduled maintenance and several causes outside Vetspire's control. For qualifying downtime lasting more than one hour, a customer may request a 5% subscription-fee credit per qualifying consecutive hour, subject to one credit per day and a quarterly cap of 25% of one month's fees. The customer must notify Vetspire and request the credit within 30 days.

Exhibit B says in-app chat support is available 9:00 a.m. to 5:00 p.m. Central Time, Monday through Friday. It lists a one-hour target initial response for a Severity 1 total or core-function failure and 72 hours for a Severity 2 high-impact problem that does not stop core functions. These are initial-response targets, not guaranteed resolution times.

Ask how after-hours critical incidents are reported, who assigns severity, when the response clock starts, which third-party failures are excluded, and whether the order improves the standard support terms. Keep an outage procedure for triage, treatment, medication, client contact, consent, charging, and later reconciliation. A 99.9% target still permits downtime, and a service credit does not restore access to a record during an emergency.

Vetspire Reviews and Complaints

Vendor-selected testimonials describe intuitive workflows and implementation experiences. They are useful sources of questions but are not a representative sample. Third-party review sites can add perspective, yet an anonymous complaint may concern an older version, a particular implementation tier, a third-party integration, a network-managed configuration, or a commercial term that differs from the current agreement.

Use review themes as test hypotheses. For any repeated praise or complaint, ask:

  • which release and date does it describe?
  • was the reviewer an independent clinic or part of a managed group?
  • which modules and integrations were enabled?
  • was the problem a product defect, configuration choice, migration issue, training gap, or third-party outage?
  • what evidence can be reproduced in a sandbox with the clinic's workflow?
  • what response, remediation, or contract term now applies?

Request three recent reference customers that resemble the buyer: one newly implemented clinic, one customer after a full year, and one that migrated from the same legacy PIMS. For a multi-location or specialty buyer, require the same scale and clinical model. Ask references about time to go live, staff adoption, data exceptions, support escalation, invoice accuracy, add-on costs, API reliability, outages, export testing, and what they would negotiate differently.

Do not ask only whether they “like Vetspire.” Ask them to demonstrate an actual reconciliation, correction, permission, report, and failed integration workflow. Evidence is more useful than sentiment.

Who Should Shortlist Vetspire?

Vetspire is most compelling for:

  • practices replacing a legacy or locally hosted PIMS with a cloud workflow;
  • teams that need simultaneous medical-record collaboration;
  • multi-location organizations that need common data with local configuration;
  • practices that value a public GraphQL API and are prepared to govern it;
  • specialty, emergency, boarding, or inpatient teams evaluating the corresponding modules;
  • organizations willing to run a structured implementation and security review.

It may be a weaker fit when:

  • the buyer needs a simple public price and self-service month-to-month purchase;
  • a critical legacy data type cannot be migrated or exported acceptably;
  • a required lab, pharmacy, payment, accounting, or imaging workflow fails the proof of concept;
  • the clinic cannot allocate implementation owners within the 12-week billing timeline;
  • internet resilience and downtime procedures are not ready;
  • the standard support window or response targets are insufficient;
  • the practice is unwilling to govern broad API credentials or AI-generated text;
  • the total cost of doctors, locations, implementation, usage, add-ons, and integrations exceeds measured value.

Compare Vetspire with at least two alternatives using the same script and scoring rubric. Give critical failures a pass/fail gate before weighted preferences. A polished interface should not compensate for an unsafe migration, missing integration, unreconciled payment, or inadequate exit path.

Vetspire Demo and Quote Checklist

Before the demo, send anonymized scenarios and require the representative to perform them in the proposed configuration. Record what is standard, add-on, third-party, roadmap, or custom.

Product

  • complete an encounter with concurrent editing and later correction;
  • order and receive labs, including an amended result and interface failure;
  • schedule, reschedule, cancel, and book online under real constraints;
  • create an estimate, invoice, partial payment, refund, and reconciliation;
  • receive inventory, use a lot, transfer stock, and report an adjustment;
  • send and opt out of messages under the clinic's consent policy;
  • show role permissions, audit events, automatic timeout, and SSO;
  • show AI source, review, correction, approval, retention, and deletion;
  • export a complete patient chart and organization-level data sample.

Commercial

  • name the subscription tier, doctors, locations, and billable-doctor rule;
  • list every included module and every excluded capability;
  • itemize implementation, migration, training, travel, and rescheduling;
  • disclose all usage, payment, API, certification, and integration fees;
  • provide three-year totals with renewal and price-change assumptions;
  • state the initial term, notice address, deadline, and remaining liability;
  • price a full validated export and transition assistance.

Security and operations

  • provide current independent assurance and penetration-test summaries under NDA;
  • identify hosting, subprocessors, encryption, key management, and backups;
  • disclose incident notification, recovery targets, and support escalation;
  • confirm API approvals, key roles, logs, limits, and deprovisioning;
  • test downtime workflows and post-outage reconciliation;
  • document AI providers, data flows, retention, and model-training restrictions.

Frequently Asked Questions

How much does Vetspire cost?

Vetspire did not publish an accessible current dollar price during this review. Its standard agreement says subscription fees are charged monthly per doctor, with doctors under ten shifts in a calendar month excluded from the count. Implementation is required, while migration, usage, integrations, API work, add-ons, taxes, and third-party services can affect total cost. Request a line-item order and three-year model.

Does Vetspire have an API?

Yes. Vetspire publishes GraphQL API documentation with production, staging, and sandbox endpoints. It covers queries and mutations across major PIMS domains and currently limits query depth to eight. The secret key can grant organization-wide read and write access, so it needs least-privilege roles, vault storage, rotation, monitoring, and revocation.

Is Vetspire cloud based?

Yes. Vetspire describes the current product as a cloud-based platform. Buyers should still test local internet resilience, printing, scanners, payment terminals, imaging connections, and downtime workflows because a cloud PIMS depends on the clinic's connectivity and third-party services.

Does Vetspire support AI scribing?

Vetspire markets an AI Suite with Scribe and Summary. The standard agreement says AI output is fallible and must be validated by the customer. Confirm inclusion, usage limits, recording consent, retention, subprocessors, audit trail, and clinician approval in the exact quote.

Can a clinic export its data?

The manual documents patient-record sharing and selected Excel or report downloads, and the agreement says customer data is owned by the customer. After termination, the standard contractual retrieval period is 30 days and transfer assistance may cost extra. Obtain an organization-wide sample export, schema, attachment set, audit history, validation process, and price before signing.

What uptime and support does Vetspire promise?

The standard agreement states 99.9% monthly availability with exclusions. It lists in-app support during weekday Central Time business hours, a one-hour target initial response for Severity 1, and 72 hours for Severity 2. Service credits require notice and a timely request. Confirm any stronger terms in the order.

Final Verdict

Vetspire is a credible, feature-rich cloud PIMS with a notably open developer reference, broad documented integrations, configurable workflows, and optional modules for AI, specialties, boarding, wellness, and inpatient care. Its public contract also gives buyers more concrete information about availability, support, security, implementation, data retrieval, and API obligations than many high-level software pages do.

The same documents explain why the purchase needs discipline. There is no dependable public price, the order form controls scope, billing has a 12-week backstop, migration is not guaranteed, add-ons and integrations can change the economics, support targets are limited, and the exit window is short.

Shortlist Vetspire if its architecture and workflow match the practice. Buy it only after a representative completes the clinic's hardest scenarios, the migration sample reconciles, required integrations pass, security evidence is reviewed, the full cost is itemized, and the signed order resolves acceptance and exit. That process—not a generic star score—is what determines whether Vetspire is worth it for a specific veterinary organization.

First-Party Sources Reviewed

Product pages, documentation, and legal terms can change. Verify the current order, pricing sheet, data terms, security evidence, and implementation scope directly with Vetspire before making a purchasing decision.