Your recipients share their badge because they are proud of it — and your organisation's name and a link to your site travel with it. On Credly that link goes to credly.com, and the click is theirs. On Sigilet it lands on a page that names you, not us — your own domain if you're on Business.
A credential is the only marketing your alumni want to post.
Nobody shares an ad. People share proof of something they worked for. Here is what that is worth, and where it lands.
1
You award it
Design the badge once, then issue it — one person, or a whole cohort from a spreadsheet. It carries your name, your logo and your criteria.
2
They share it
No account to create, no claim flow, no wall. A link that works, a LinkedIn button, and a badge file that carries its own proof. The share happens because nothing is in the way of it.
3
It points home
The verification page carries your name and links to your site — your own domain on the free plugin, and on Cloud's Business tier. Every share is a person who actually did your training, recommending you to the colleagues most likely to do it next.
This is the part worth being precise about. On Credly, the badge your recipient shares lives at credly.com/badges/… — the click, the visit and the search equity land on their domain. With Sigilet the click lands on a page that names you, not us: your logo, your name, a link to your site. The free plugin always serves that page from your own domain; the hosted service does too on Business, and on Community it's still branded as you, just served from ours. And because we ask your recipient for nothing, they are still there at the moment they would have shared: every account wall loses people exactly when they were proudest.
What we will not claim: that we have an audience to lend you. We have no recipient network and no badge directory, and any reach you get here is your own people telling their own contacts. That is worth more anyway — but it is yours, not ours to promise.
Two ways to run it. One of them is free.
Same standard, same "no account for your recipients", same verification page branded as you, not us. The difference is who runs the server — and, on Cloud, whether that page lives on your own domain or ours.
Self-hosted · WordPress
Sigilet for WordPress
Freeno expiry, no quota, no upgrade wall
Runs on the WordPress site you already have. Issue badges, host their verification pages on your own domain, revoke, expire, and hand out baked badge files — none of it time-limited and none of it metered.
Your infrastructure, your database, your domain
Recipients' email addresses are never stored — only a salted hash
Open Badges 2.0, finished today
Live in the WordPress.org directory. Search for Sigilet in Plugins › Add New, or install it from the directory — it updates like any other plugin.
Awarding a whole cohort from a spreadsheet? Sigilet Pro adds CSV bulk award and a paced send queue, A$149/year for one site, and everything above stays free.
Fully managed · Australian hosting
Sigilet Cloud
From A$139per month, published below
We run it, in Australia. Signed Open Badges 3.0, hosted verification, and credentials that keep verifying even after you stop paying us.
Nothing to install, update, back up or patch
Native Open Badges 3.0, with a 2.0-compatible view
Your own issuer domain on the Business tier
In build. The first 20 tenants lock their price for good.
Already using the WordPress plugin? Cloud is its managed counterpart, not a replacement — you can stay where you are.
And they keep working after you stop paying.
A marketing channel is only worth having if it is still there next year. Four things make that true rather than promised — these describe Sigilet Cloud. On the WordPress plugin the same durability comes from a simpler place: it is your server, so nobody can switch it off but you.
The credential carries its own proof
Open Badges 3.0 signs each credential cryptographically at issuance. Anyone can check it against your published issuer key — no call to our servers, no dependency on a link staying alive. That is what makes the rest of this page possible to promise.
They stay online after you stop paying
Cancel and your existing credentials keep serving, free. You also get a full export — every credential as a portable file — as a condition of cancelling, not as a favour. A credential your recipient put on their CV should not expire because of your budget cycle.
Your recipient is not the product
No account to create, no profile to claim, no marketing list. They get a link that works and, if they want it, a button to make it public or take it down. Nothing is indexed by search engines until they choose it.
The data sits in Australia
Australian infrastructure for the Cloud service, with the one exception named plainly: card payments run through an overseas merchant of record, so we never hold your card details. We would rather list the exception than imply there isn't one.
Two prices. Both of them published.
Sigilet Cloud pricing at launch, in Australian dollars. Not "contact us", not "priced for every budget" — the actual numbers, so you can decide without a sales call.
Community
Associations, member bodies, non-profits and registered charities
A$139/month
or A$1,390/year — ten months, not a percentage off
2,500 credentials a year, unlimited badge designs
3 staff users
Bulk issuance from a spreadsheet, with dispatch reports
Signed Open Badges 3.0, hosted verification, baked badge images
Revocation, expiry, and full export whenever you want it
Business
Commercial training providers, RTOs and workshop organisers
A$329/month
or A$3,290/year — ten months, not a percentage off
10,000 credentials a year — four times the volume
Unlimited staff users
Your own issuer domain — the verification page is served from your domain instead of ours
Everything in Community, including bulk issuance
Priority support
Community is not Business with a discount applied. Business buys volume, a whole team, and the verification page on your own domain — what a commercial issuer needs and an association mostly doesn't. Each price is set on what that tier is worth, which is why we can publish both side by side instead of quoting one and discounting from it.
Non-profit pricing is listed, not on application. Enter your registration number at checkout and take the Community price immediately. We spot-check afterwards. A hidden non-profit rate is just "contact sales" wearing a different hat.
No per-badge fees, ever. Not per award, not per badge design, not per recipient. If you outgrow an allowance you move up a tier — the bill never grows by the credential.
First 20 tenants: your price never rises.
Whatever you sign at is what you pay, for as long as you stay — plus a standing say in what we build next. A locked price rather than a percentage off, because a discount implies a list price we were pretending to charge.
How that differs from the incumbents.
Every competitor cell below was checked against their own current documentation on 20 August 2026, and each is sourced. Where they beat us, we say so.
Feature
Sigilet at launch
Credly
Parchment ex-Badgr
Recipient needs an account
No
Yes — the recipient creates an account and confirms their email before they can accept the badge 1
Yes — one customer publishes their tier as US$500 per badge class plus US$3 per award 4
Credentials keep working after you stop paying
Yes — they stay online free, and the signature verifies without us
Not committed
Free issuing ended 31 December 2025; issuing now needs a paid subscription 5
Export of everything you issued
Yes — and mandatory on cancellation
Not committed
Not committed
Data hosted in Australia
Yes
No — United States
Yes
That last row is a tie, and it matters that we say so: Parchment stores in Australia too. In-country hosting is a real difference against the American platforms, not against every competitor, and we are not going to imply otherwise. What no incumbent offers is the combination of the other five rows.
Credly, pricing page — no figures published; a demo request is the only route. We have deliberately not repeated the dollar figures that circulate second-hand, because we cannot verify them.
University of Wisconsin–Madison, Digital Badges — the institution publishes its own Parchment tiers, including the per-badge and per-award fees.
Badgr's free issuing tier closed on 31 December 2025; Parchment badge issuing now requires a paid subscription.
One thing we have stopped claiming: that we are the only ones doing Open Badges 3.0. Credly announced OB 3.0 support in October 2024 and other platforms now issue it too. The version number was never the point — what matters is the consequence, which is that a signed credential verifies with no server of ours involved. That is the fourth row.
Comparing us to Credly in particular?Read the longer comparison, which covers whether your recipients need an account, what happens to your credentials if you stop paying, and which country the data sits in.
Join the waitlist
The WordPress plugin is out now, so there is nothing to wait for: install it free from the directory. This list is for Cloud, the hosted version. Tell us you want it and we'll write to you the day it opens. Nothing else, ever.
You're on the list — we'll be in touch as each option opens up.
