Start every morning knowing your e-resources work.
Automated E-Resource Verification.
PatronPath simulates real patron behavior to verify your critical e-resources are accessible. We run comprehensive daily audits so your team starts every day knowing exactly what is working and what isn't.
Why wait for an angry email?
Libraries invest heavily in digital resources, yet the first sign of an outage is often a frustrated email from a patron, faculty member, or staff user. By then, dozens of others have already hit a dead end and either given up or gone elsewhere.
PatronPath flips the model. Instead of reacting to tickets, you receive a daily verification audit that confirms exactly what is accessible before you even open your inbox.
We navigate the mess so you don’t have to.
We don’t just ping the URL. We act like a patron.
- 1
Step 1: Login
We securely authenticate through your existing remote-access setup (proxy, SSO, or other authentication), simulating a remote patron (student or community member).
- 2
Step 2: Navigate
Our engine follows the full redirect chain, handling the pop-ups and vendor handshakes that simple link-checkers miss.
- 3
Step 3: Verify
We verify that the final vendor page successfully resolves to the target resource. This ensures we’re confirming valid access rights, not just a successful redirect.
Get a screenshot-rich report every morning.
Send this directly to the vendor to skip the “it works on my machine” argument. Includes timestamps, error codes, and screenshots of the failure.
Each failure report includes timestamped screenshots, HTTP error codes, and step-by-step navigation evidence for vendor support tickets.
No integrations. No plugins. No IT projects.
Many verification tools require you to wire directly into your authentication stack, triggering security reviews and endless maintenance. PatronPath is different.
We sit outside your network.
We run on our own managed infrastructure. Because we access your resources exactly like a remote patron does, we don’t need API keys, firewall exceptions, or server access.
Zero installation
We run entirely as a managed service.
Resilient to change
As long as remote access still works for a typical patron, our tests can usually keep running with minimal adjustment.
Secure by design
We use test-only credentials and never store patron data.
Who It's For
E-Resource Librarian
Stop spending your morning triage verifying claims. Get a prioritized list of access failures with evidence attached, so you can file vendor tickets in seconds.
Systems Librarian
Get reproducible failure paths without installing local agents or debugging end-user screenshots.
Library Director
Protect your budget. Ensure the resources you pay for are actually reachable by the community you serve.
Join the beta pilot program
We are inviting a small cohort of academic and public libraries to partner with us for our beta launch.
The pilot offer:
- White-glove setup: We configure your eligible A–Z list resources for you.
- Minimal IT involvement: No server access or API keys needed.
- Up to 2 months free: Full access to the verification engine during the pilot period.
Your commitment:
- One 15-minute feedback call per month.
- Permission to publish a joint case study if we successfully detect errors for you.
FAQ
What is PatronPath?
PatronPath is an automated digital resource assurance service for libraries. Unlike simple uptime checks, it acts as a synthetic patron, simulating the complete login and navigation journey to verify that off-campus users can successfully access licensed databases and journals.
How does User Journey Testing work?
User Journey Testing (or Synthetic Transaction Monitoring) verifies the entire access path rather than just a single URL. PatronPath automates this by executing real browser sessions that navigate the library portal, pass through authentication (SSO/Proxy), and validate the final vendor resource loads correctly.
Why is E-Resource Verification important?
Libraries invest heavily in digital collections, but complex authentication chains often fail silently for off-campus users. Automated E-Resource Verification detects these "silent failures"—where a server is up but access is denied—ensuring reliability without relying on patron complaints.
Do we have to host or maintain anything ourselves?
No. PatronPath is a managed assurance service. You don’t install agents or stand up servers. We operate the tests on our own managed infrastructure and deliver reports to your team.
What exactly does PatronPath verify – and what doesn’t it?
We focus on the patron access journey to your licensed e-resources: A–Z lists, remote-access flows (proxy/SSO), and vendor platforms. We do not replace your ILS, discovery layer, or campus IT monitoring. We don’t track general network uptime or server health; we test whether a typical patron can actually reach and use the content you’re paying for.
Do you test remote access specifically?
Yes. Most access failures happen off-site. Our tests are designed around the remote-patron journey, using test accounts you provide, so we can see what your community sees when they’re not on campus or in the building.
How do you handle credentials and patron data?
We only use test credentials that you provide for verification. During the beta we do not ask for or process patron names, emails, IDs, or any real patron identifiers. Credentials are stored securely with least-privilege access, and logs/screenshot retention is limited and documented on our Security and Privacy pages.
Will this flood us with alerts?
No. During the beta, we typically run checks on a scheduled basis (for example, nightly) and send batched, screenshot-rich reports, not one email for every transient error. We work with you to focus on high-impact resources and keep noise low.
Do you open vendor support tickets for us?
No. You keep full control of vendor relationships. PatronPath gives you vendor-ready evidence (URLs, timestamps, error text, screenshots, and environment details) so you can file a clear ticket in seconds instead of spending hours reproducing the issue.
What do you need from our IT or systems team to get started?
Typically: a small number of test accounts, agreement on which networks or remote-access paths to test, and a quick security review. There’s no on-prem install or firewall change required for the desktop-run beta; details are documented on our Security page.
How soon will we see value?
Libraries can start seeing actionable insights within the first few days of verification. In many pilots, the first report already surfaces misconfigurations or broken links that hadn’t yet generated patron complaints.