Your layout
Upload the PDF you already designed. Names and dates go where you marked them.
Verifiable certificates
Your PDF, a spreadsheet, and Amazon SES. Twenty-five certificates land on a new account.
Organizers already on it
The work
Upload the PDF you already designed. Names and dates go where you marked them.
One CSV. One queue. SES takes the batch so you are not exporting by hand.
The code on the certificate is the same one on the public record. Revoke, and it says so.
Who it’s for
A chapter weekend, a six-week course, or a two-day summit. The sheet changes. The send does not.
Winners, participants, and volunteers from one sheet. Sent before the closing stage is over.
A completion certificate for every person who finished, with a page their employer can open.
Speaker, mentor, and attendee files without a separate export for each role.
How a batch goes out
Drop the roster. We read names, emails, and the award line.
| Name | Award | |
|---|---|---|
| Aria Montgomery | aria@stanford.edu | First place |
| Devansh Sharma | devansh@mit.edu | Completion |
| Elena Rostova | elena@cam.ac.uk | Keynote |
Column in the file, place on the PDF. That is the whole mapping.
A short note, the PDF, and the code that opens the public page.
TO ARIA MONTGOMERY
Aria, the certificate is attached.
Aria_Montgomery.pdf · AC-2026-W091
SES sends the batch. A hard bounce puts that credit back.
Same evening
2,400 rows. Bad emails pulled first.
PDFs and letters go out on SES.
Someone already opened the record.
Bounces returned. Credits stay.
On the desk
Syntax, blanks, and disposable inboxes get caught before you hit send.
Pick the name, the award, the event. The rest of the sheet stays still.
One click from the campaign. LinkedIn sits on the public record.
Launch a campaignThe inbox
From organizer@hackindia.org
Aria, first place is on the certificate. The code printed on it opens the public page.
AC-2026-W091
After you hit send
The public page
Anyone with the identifier can open the same page. Revoke one name and that page is the thing that changes — you do not resend the batch.
On record
National AI Buildathon 2026
First place, full-stack track
Why this
The PDF
We fill the spots you marked. No clip-art certificate dumped on the cohort.
Delivery
Inbox, public page, or the file. Same certificate either way.
Registry
Employers, participants, you. One revoke updates the page.
Credits
Hard fail, credit returns. You do not pay for a mailbox that never existed.
Your PDF
Upload the certificate you designed. We do not swap it for ours.
Mark them once. Every row fills the same places.
Each name becomes one copy of your file.
A code on the PDF. The same one on the public record.
From organizers
We sent 1,800 winner and attendee certificates the same night.
“The public page is what I forward to sponsors when they ask if the award is real.”
“Credits sitting from last semester still worked. We did not buy a second pack.”
Keep the file and the list. That part is already yours.
Fill, send, and keep a page. A bounce does not cost a credit.
Features
Features
Features
Features
Questions
Credits, your PDF, a bounce, and sending from your domain.
No. Free credits and paid packs stay on the account until you send them.
Yes. Upload it, mark the name and date, and each row fills one copy.
A hard bounce returns that credit. You are not charged for a mailbox that never existed.
Yes, on paid plans. Connect the domain, add the DNS records, and SES sends as you.
The public page has a link the recipient can use. You do not paste certificates in by hand.
Ready when the list is
Upload the sheet tonight. People can open their page in the morning.