Notive Health
← Back to blog

Hint Core vs Notive Sponsors: 11 Differences for DPC Clinics in 2026

· 9 min read · Notive Health

Hint Health defined employer-sponsored Direct Primary Care billing. Their Hint Core product has been the default rail for clinics that contract with employers to cover staff DPC memberships — Stripe-backed invoicing, eligibility sync, the works.

Notive Sponsors is the alternative we built into our EHR. Same lifecycle (contracts, rosters, eligibility, opt-in, COBRA-style continuity), bundled with the platform clinics already use to chart.

This post is the side-by-side. Eleven concrete differences, each one sourced against Hint’s own public documentation.

The headline up front: as of 2026-05-24, Hint Core’s entry tier starts at $100/month with no eligibility sync. Their tier with eligibility sync starts at $600/month. Notive includes everything on this list free with every plan.

The Frame: Bundled in the EHR, Not Bolted On

Before the eleven differences, the bigger structural difference: Hint Core is a separate platform. You sign into Hint to run the sponsor side and into a different EHR to run the clinical side. Notive folds the sponsor side into the EHR your team already uses, with one login, one source of truth, and a single audit trail.

That sounds like a UX argument, but it has compliance implications. The plan-sponsor firewall under 45 CFR §164.504(f) requires that sponsor administrators see eligibility and billing only — never patient health information. With two separate platforms, you have to trust two access-control systems. With one platform and an internal database boundary, the firewall is enforced once, at the data layer. We talk about the architecture below.

1. Cost to the Clinic

Hint Core’s published pricing has three tiers:

  • Core Growth. $100/month base, includes 100 members. $40/month per additional 50 members. Card transaction fees 2.75% + $0.30 + 1% AmEx surcharge. ACH 0.75% + $0.25, capped at $5 per transaction. Zero AutoSync feeds included.
  • Core Scale. $600/month base, includes 500 members. $150/month per additional 250 members. Lower transaction fees. 3 AutoSync feeds. Adds network management, Hint Connect rental, commission tracking, engagement tracking.
  • Core Enterprise. Starts at 1,000 members. Custom pricing. 10 AutoSync feeds. Adds custom MSA/BAA, unlimited API access, dedicated account management, white labeling.

Notive Sponsors is free with every Notive plan. There is no per-member fee for sponsor management, no AutoSync paywall, no transaction-fee tier ladder. Card and ACH processing run through Stripe at Stripe’s standard rates.

If you have 200 employer-sponsored members and you’re on Hint Core Growth, you’re paying $100 + ($40 × 2) = $180/month plus transaction fees. Notive: $0 added to your existing plan.

(Source: hint.com/core/pricing as of 2026-05-24. Full quoted captures retained internally and available on request.)

2. Eligibility AutoSync Is Paywalled

This is the line item small DPCs feel hardest. Hint AutoSync is the feature that ingests employer roster files automatically — without it, you process eligibility manually every time an employer sends an update.

Hint Core Growth does not include AutoSync. You have to upgrade to Scale ($600/month minimum) to get any feeds at all. Scale caps at 3 feeds. Enterprise (1,000+ members) gets 10.

Notive Sponsors includes eligibility sync at every plan, with no feed cap and no upgrade required. If you have one employer sending you a roster, that’s a feed. If you have twenty, those are twenty feeds. Same plan price.

3. Roster Ingest: CSV Upload

Hint AutoSync supports CSV files delivered via SFTP. Notive supports CSV upload in the portal directly. Both work; Notive’s path is slightly faster for ad-hoc updates because it skips the SFTP step.

This is a tie on capability, but Notive’s UX is one fewer integration step for a manual upload.

4. Roster Ingest: REST API

Notive offers REST API ingestion on every plan. Hint offers it too, but their support article on AutoSync setup only describes CSV-via-SFTP — programmatic access shows up as a line item under “Unlimited API access” on Core Enterprise tier, which is custom-quoted and starts at 1,000 members.

If you’re an employer or TPA that wants to push eligibility updates programmatically into the clinic’s system, Notive supports that out of the box; Hint pushes you to Enterprise.

5. Roster Ingest: EDI 834 — Notive Only

Hint’s published AutoSync documentation describes CSV file ingest via SFTP. There is no mention of EDI 834 (the X12 healthcare enrollment standard most large-employer payroll systems and TPAs export natively).

Notive supports EDI 834 ingestion on every plan. This matters for one specific scenario: an employer’s HR team uses a payroll or benefits-administration system (Workday, ADP, BambooHR, Gusto’s enterprise tier) that natively exports 834. With Hint, your DPC clinic has to write a transform from 834 to Hint’s CSV spec, run it on a schedule, and maintain it. With Notive, the 834 lands directly.

This is a real differentiator for clinics serving employers above 200 employees, where 834 is the default eligibility format.

6. SFTP Delivery: Feed-Count Cap

Hint’s SFTP delivery (the canonical AutoSync flow) is capped at 3 feeds on Scale and 10 on Enterprise. Each feed is one employer/TPA relationship. If you grow past the cap, you upgrade tier or compress multiple employers into one feed (operationally messy).

Notive does not cap SFTP feeds by tier.

7. EHR Integration

Hint Core is a separate platform. Single sign-on into your EHR does not log you into Hint, and vice versa. Patient records are linked by external ID; clinical context lives in the EHR; eligibility and billing live in Hint.

Notive Sponsors is the EHR. Sponsor admins log into a separate sponsor.notive.app surface (because they shouldn’t see PHI), but staff with both clinical and sponsor responsibilities log in once. The roster row for a patient is one click from their chart.

8. HIPAA Firewall Implementation

Both companies are HIPAA-compliant — that’s table stakes. The architectural question is how the plan-sponsor firewall is enforced.

Hint’s public documentation describes the firewall as a feature (“sponsors see eligibility and billing only”) without detailing the enforcement layer. The standard implementation in cross-platform setups is application-level filtering: route handlers check the user role and refuse to serve PHI fields.

Notive enforces the firewall at four independent layers:

  1. Database role isolation. The sponsor service’s Postgres role has no SELECT privilege on clinical tables. A misrouted query produces a permission error, not a privacy incident.
  2. Service-process isolation. Sponsor-service runs as a separate FastAPI process with no clinical-DB connection at all.
  3. Response-schema allow-listing. Pydantic schemas on the sponsor side define exactly which fields can be serialized; anything else is dropped.
  4. Frontend-bundle import boundary. The sponsor portal’s React bundle cannot import any component that displays clinical data — enforced by a Biome lint rule, so a developer mistake fails the build.

This is more architecture than most clinics need to evaluate. But if you’ve ever been through a HIPAA audit, the difference between “filtered at the query layer” and “filtered at the database-role layer” is meaningful.

9. Payment Processing

Hint’s current Terms of Service (Section 1.11(a)) identifies Rainforest Pay as the active payment processor. Their developer documentation still references Stripe Payment Elements for tokenization, which suggests a hybrid setup: Stripe handles card-data tokenization (so card numbers never touch Hint’s servers), Rainforest handles ledger and settlement.

Notive uses Stripe end-to-end. Tokenization, settlement, invoicing, subscription billing, dunning. One processor.

The practical implication is small for most clinics. The architectural implication is that there’s one fewer vendor in your billing path with Notive. If your finance team is auditing payment flows, fewer vendors is fewer reconciliation surfaces.

10. COBRA-Style Continuity

When an employer’s sponsorship for a patient ends (employee leaves the company, employer terminates the contract, employer goes past-due), the patient needs an offer to continue their DPC membership on their own.

Both Hint Core and Notive Sponsors support continuity workflows. Hint calls theirs “term member” handling; Notive supports a continuity window (configurable per contract, default 30 days) during which the patient can accept self-pay billing on their own card without a gap in care.

This is a functional tie. Both platforms do the right thing for the patient.

11. Custom MSA/BAA

Hint Core’s custom MSA/BAA is a Core Enterprise feature only. If you’re on Growth or Scale, you sign Hint’s standard agreements.

Notive offers custom MSA and BAA on every plan. For small clinics whose legal counsel has specific language requirements, this is meaningful.

How to Migrate from Hint Core to Notive Sponsors

If you’re already on Hint and the math above pencils out for a switch:

  1. Inventory active contracts. Export the employer list, contract terms (effective dates, per-employee pricing, payment arrangement, billing day), and the current eligibility roster from each one.
  2. Map the data. Hint’s eligibility export uses External ID as the stable identifier. Notive’s import accepts that field directly — no remapping required if you keep the same External IDs.
  3. Set a cutover date. Choose a billing cycle boundary. Run the final Hint invoice for the closing cycle; start Notive billing the next cycle.
  4. Notify sponsor admins. Your employer contacts log into the new portal at sponsor.notive.app instead of Hint. Same data, new URL.
  5. Cancel Hint subscription on the last day of the closing cycle. Don’t cancel earlier — you need access to historical reports for finance reconciliation.

We’re selecting design-partner clinics for early-access onboarding now. Reach out via the Sponsors page and we’ll match timing to your readiness.

The Bottom Line

Hint Core defined this category, and they still win on a handful of features. But for the typical small or mid-sized DPC clinic in 2026 — under 1,000 employer-sponsored members, no need for divisions or white-label, billing through Stripe natively — Notive Sponsors removes the $100-$600/month line item from your software stack and folds the workflow into the EHR your team already uses.

If you’re paying Hint Core today and want to see what migrating to Notive looks like for your specific contracts, the Sponsors page has the early-access form. Tell us about your current setup and we’ll send you a side-by-side cost comparison for your roster.

Comparison reflects Hint Core’s publicly listed pricing and feature inclusions as of 2026-05-24. Dated source captures retained internally and available on request. We update this post when Hint changes its tiers.