On this page
- Cost that does not grow with your success
- Your data stays yours
- Certificate verification under your own name
- What you need for self-hosted certificate verification
- Self-hosted certificate verification vs SaaS at a glance
- When a SaaS platform might suit you better
- Moving to self-hosted certificate verification
- Frequently asked questions
Short answer: Self-hosted certificate verification on WordPress means issuing and checking credentials on your own site: no per-certificate fees, records stay in your own database, and verifiers land on your domain instead of a third-party platform.
Digital credential platforms are convenient – until the invoice grows with every cohort, or you need to move your records somewhere else. Self-hosted certificate verification on your own WordPress site keeps the records, the domain and the costs under your control.
Key takeaways
- No per-credential fees: issue as many as you need.
- Records stay in your own database.
- Verification happens on your domain, under your brand.
Cost that does not grow with your success
Most hosted platforms price by the number of credentials or learners. A plugin licence is priced by the number of websites, so issuing your thousandth certificate costs the same as your first.
Your data stays yours
Holder names, emails and records live in your WordPress database, under your existing hosting, backups and privacy policy. Backups download straight to you and are never left in public folders.
Certificate verification under your own name
When an employer scans a QR code, they land on your website. That builds trust in your organisation rather than in a platform’s brand – and keeps visitors on your site.
What you need for self-hosted certificate verification
- WordPress 6.4 or newer and PHP 7.4 or newer.
- Any theme or page builder.
- An SMTP plugin if you want certificates emailed reliably.
Self-hosted certificate verification vs SaaS at a glance
| Self-hosted on WordPress | SaaS platform | |
|---|---|---|
| Cost model | A licence per site, so costs stay flat | Often per credential, so costs grow |
| Where data lives | Your own database | The provider’s servers |
| Verification domain | Your own domain | Usually the provider’s |
| Design | Your theme and brand | Provider templates |
| Leaving | Your data simply stays put, because it is yours | Export and migrate |
In short, self-hosting trades a little setup for long-term control. Also, it keeps every verification on your own brand, so employers learn to trust your domain.
When a SaaS platform might suit you better
To be fair, hosted platforms suit some organisations well. For example, if you have no website at all, or you need a learner wallet across many issuers, a platform can be simpler. However, most organisations that already run WordPress get more control, a lower long-term cost and stronger branding by verifying on their own site.
Moving to self-hosted certificate verification
- First, export your existing credentials from the old system as a CSV.
- Next, import them into CertiQR, keeping the existing certificate numbers.
- Then set up redirects from the old verification links if you can.
- Finally, announce the new verification page to holders and employers.
Because CertiQR keeps your existing IDs, certificates that are already printed can still be checked on your new page.
In addition, the WordPress hardening guide is a useful, independent reference if you want to read further.
Frequently asked questions
QIs self-hosted verification secure?
Yes. Each record carries an issuer signature so changes made outside the plugin show up as altered, and verification logs store hashed IP addresses rather than raw ones.
QWhat happens if we stop paying for the licence?
Your records and verification page keep working. A licence covers updates and support.
QCan we move to a new host later?
Yes. Take a full backup and restore it on the new site, including settings and certificate files.
Ready to try it?
Run certificate verification on your own WordPress site with no per-credential fees. Try CertiQR free for 7 days.
Does self-hosting slow my website down?
No. Verification pages are light, and caching handles normal traffic easily. Also, CertiQR only loads its files on the pages that use them.
Who handles updates for a self-hosted plugin?
You install updates from the WordPress dashboard. With a licence, updates arrive automatically like any other plugin.
We build CertiQR, the WordPress plugin for issuing certificates and verifying them with a QR code. We write about credentials, verification and running a certificate programme.
