Citation HP-007: urSynergy does not sell animal records, run an ad network against care surfaces, or gate the open standard.. Records are the content flowing through the infrastructure; records are never the product.
The commitment is structural, visible in the revenue model itself, and auditable. What urSynergy does not do is as load-bearing as what it does. Every future revenue consideration is checked against the negation list before being adopted.
// records belong to the animal. stewardship to the humans caring for it.
// infrastructure is urSynergy's to operate, never to own.
// acquisition, not profit
Physical NFC/QR smart tag (urSmartID) sold direct-to-consumer at $24.99 via Amazon Prime. Tag economics are break-even to slight margin; the tag is a customer acquisition instrument, not a profit center. The customer pays urSynergy to acquire them, effectively inverting typical SaaS CAC.
// the core
Professional platforms — urVetMD clinic CRM, urBreed premium breeder tools, urPetLicense white-label municipal licensing, theVetRegistry credential verification queries. Recurring subscription, per-tenant, per-seat where appropriate. The durable revenue core.
// patent-gated and operations-gated
Per-transaction revenue on flows urSynergy operates the rails for — prescription routing between vetscript and animalRx, marketplace fees on urBreed commercial transactions, rehoming-fee splits enforced at the database constraint layer (including 0% to rehomer — zero-profit structurally enforced), vet telehealth splits, Stripe Connect-backed destination charges.
// layered on installed base
Subscription and service revenue layered on the physical-tag installed base — auto-replenishment for lost or damaged tags, potential premium contextual access tiers, potential printed-recovery-poster service. Most extensions post-launch.
// ad boundary enforced
Revenue from the video content area only. Ads, creator monetization, and donations all live in the designated commercial zone, structurally separated from care surfaces at the routing layer. Creator revenue share via Stripe Connect; donations routed directly; live-streaming cost recovered through tiered subscriptions.
// partnership-driven
Partnership-grade revenue from institutions with long procurement cycles — academic veterinary programs pursuing curriculum integration and research partnerships; PIMS and vendor integration licensing; research institution data licensing (aggregate, de-identified only); insurance carrier integrations; municipal enterprise tier. Emerges as the platform matures and institutions seek integration.
// portfolio-gated
Revenue from the patent portfolio — licensing on negotiated terms, formal partnership structures where a counterparty gains use-rights, and acquisition exposure on the prescription-routing architecture specifically (the highest-market-exposure patent). Licensing is not published as a tier; it is negotiated per-counterparty. Acquisition is an exit pathway, not an operating revenue line.
Records are never the product
Revenue is extracted from infrastructure urSynergy builds and IP urSynergy authors — never from the records that flow through the infrastructure.
Care surfaces are ad-free
Records, messaging, animal social profiles, and care workflows are ad-free. Advertising exists only in the designated video content zone, enforced at the routing layer.
Standards are published, not gated
USAT1024 is free to use with required citation. AWDPS is a separately authored arm's-length standard; urSynergy complies, does not own.
APIs are open under standards compliance
Vendors implementing USAT1024 can integrate without permission. Municipal systems connecting to their own jurisdiction's records do not need urSynergy as an intermediary.
Consent is non-negotiable
Every record flow between stewards is gated on explicit, contextual, revocable owner consent. No revenue fork is permitted to bypass this.
Platform sovereignty is real
Tenants — clinics, breeders, municipalities, authorities — retain authority over data within their scope. urSynergy operates the infrastructure; tenants operate their slice.
This page describes what the forks are and why they take the shape they do. It does not publish pricing, projections, acquirer names, or confidential unit economics — those live in tiered partner and investor materials derived from the canonical revenue architecture reference.
