01
Choose the people-served range that matches the program you can actually supportPricing is based on people served per month so the service level tracks with real participant demand instead of looking like a one-off purchase.
Pricing
Choose the partner service level that fits the rollout you are actually trying to run
Blacklight pricing is built around people served per month because institutions are usually evaluating more than a file count. They are deciding how much capacity, structure, and rollout support the program needs to launch credibly across real teams and locations.
This page is meant to help you pick the cleanest launch level, not force you through a checkout before the program fit is clear.
Use review when higher volume, invoicing, multi-tier access, or rollout complexity means the account should not be treated like a standard pilot.
How to choose
Pricing should answer capacity, package depth, and rollout fit
The strongest partner decision is not just picking a number. It is matching monthly capacity, service depth, and rollout complexity so the program starts in the right lane.
02
Decide whether one standard service level is enough for the rolloutMost pilots start with one package level. Custom review is there when you need broader access, multiple tiers, or a more specialized launch shape.
03
Review whether onboarding, invoicing, or rollout support changes the pathThe review path keeps trust, billing, and launch support aligned before activation so the account starts cleaner and scales more predictably.
Standard service levels
Standard monthly lanes for people served
Standard partner plans are designed for programs that can launch with one service level and one monthly capacity lane. Higher volume, multi-tier access, invoice terms, or nonstandard rollout structure stays review-based.
Pick the closest clean lane first. Escalate only when the rollout shape stops being standard.
Most programs do not need a custom commercial path on day one. Use review when the launch adds invoice terms, higher monthly volume, or more operational complexity than a standard pilot should carry.
150+ people served/month
Use commercial review for higher volume, multi-tier access, invoice terms, or nonstandard rollout needs.
Monthly capacitySingle service laneReview when nonstandard
The clearest starting point for libraries and workforce teams that want room to grow.
Recommended starting pointBest for a lighter launch with one core program or a smaller branch footprint.
Designed for broader partner adoption with more participant volume in one billing cycle.
Onboarding options
Add rollout support when the launch needs more than a standard portal setup
Standard self-serve onboarding stays available in the partner portal. Higher-touch rollout help is available when the launch needs support across multiple locations, internal teams, approvals, or early implementation review.
Keep onboarding light unless the rollout really needs coordinated support.
The goal is not to turn every launch into a services engagement. Add support only when the program has enough moving parts that a simple portal setup will not be the cleanest path.
Self-serve firstAdd support when rollout expands
Kickoff guidance, setup review, and short post-launch follow-up for lighter rollouts.
Kickoff session, setup help, hosted-link and embed guidance, trust support, and launch follow-up.
Multi-stakeholder rollout planning, implementation review, and custom billing coordination.