An Aptenova-owned product
A connected journey from exam access to a verifiable credential. DevCerts brings voucher purchases, Askium-powered assessments, candidate results and certificate verification together in one product.
Vouchers
Candidates buy voucher balance first, then spend one voucher to prepare access for a selected certification.
Askium
The real exam runtime stays outside DevCerts; launches and results are connected through explicit integration contracts.
Proof
Passed attempts become public certificate records with status, issue data, credential IDs, and downloadable PDFs.
Inside DevCerts
Choose a chapter to see the interface and the work behind it.
The workspace brings voucher balance, ready exams, and issued credentials into one overview.
Permits show launch availability, expiry, retry timing, and previous attempt state.
Issued credentials expose the holder, score, credential ID, public verification page, and PDF download.
B2B platform development
DevCerts is built around a clear boundary: it manages certification commerce, access, issuance, and proof, while the actual exam session and scoring are handled by Askium. It shows how Aptenova handles platform rules, payments, external services, identity, and public verification in one product.
Public pages explain the certification catalog, prices, exam rules, methodology, company use cases, legal policies, contact paths, and blog content without promising guaranteed outcomes.
Candidates register, buy vouchers, keep balance available, and convert one voucher into a launch-ready permit for a specific certification when they are ready to take it.
Exam permits orchestrate Askium launch links, validity windows, retry policy, cooldown rules, and the candidate-facing status around prepared or completed attempts.
Successful webhook-confirmed results issue certificate records with immutable candidate snapshots, score data, credential identifiers, public verification pages, and PDF output.
Product screens
Captured from the current DevCerts product: homepage, certification catalog and details, candidate workspace, exam access, issued certificates, and blog.
Follow the candidate from their workspace to exam access and an issued credential. These are existing product screens you can open and inspect.
Why it works this way
DevCerts separates payment from a specific exam by selling voucher balance first. The candidate spends one voucher only when preparing a permit for a concrete certification, and the system keeps ledger history around that movement.
Askium owns question delivery, time limits, navigation, scoring, and result calculation. DevCerts owns catalog, permit state, launch orchestration, result intake, retry rules, and certificate issuance.
Public certificate pages are the primary proof surface. PDFs are useful for sharing, but the live verification page carries the current credential status, issue data, result summary, and certificate identifiers.
Explore the capabilities
The strongest part of the product is the connected certification lifecycle: catalog, payments, permits, external exam delivery, result intake, certificate issuance, and public verification all share one domain model.
Certification pages keep technology labels, exam scope, preparation topics, SEO metadata, certificate wording, and catalog order separate enough to manage real offerings.
The product sells voucher balance, not guaranteed certificates. A voucher is spent only when a candidate prepares access for a specific certification exam.
DevCerts prepares exam access, launches candidates into Askium, receives result webhooks, and derives passed or failed state from the configured score threshold.
Exam permits track prepared, launch-ready, completed, expired, retry-ready, cooldown, and retry provisioning states without mixing them into payment records.
Issued certificates expose public verification pages, credential IDs, status, issue dates, score summaries, downloadable PDFs, and verification-oriented sharing surfaces.
Certificate proof payloads, signing keys, JWKS output, verification keys, comparison endpoints, and verification logs make public credential checks auditable.
Credential pages can produce downloadable PDFs, public share images, QR codes, template-based certificate views, and share-oriented verification links.
Candidate workspace flows cover voucher balance, ready-to-take exams, attempts, certificates, billing, profile identity, social sign-in links, and company-managed access.
Company owners manage members, role changes, voucher transfers, company wallet balance, company-funded exam permits, action logs, and member-linked credential access.
Voucher purchase orders, provider switching, Stripe and Paddle webhook intake, payload sanitizers, payment operations, and ledger entries keep commerce state explicit.
Profile flows cover certificate identity fields, password changes, two-factor setup, recovery codes, social provider links, and active-user access enforcement.
Blog articles, topics, static legal pages, certification landing pages, cached public renders, sitemap output, and IndexNow submissions support acquisition content.
Filament-backed administration supports certification exams, users, payments, vouchers, certificate records, runtime settings, blog content, and inbound support operations.
Business widgets, integration health checks, history snapshots, user action events, payment webhook events, and support conversations expose what happened after each state change.
Capabilities
Public surface: homepage, certification catalog, individual certification pages, prices, company information, exam rules, methodology, blog, contact, legal pages, sitemap, and robots output.
Candidate workspace: dashboard, voucher balance, buy-voucher flow, available exams, ready-to-take permits, attempts, certificates, billing, companies, profile identity, and two-factor setup.
Certification domain: voucher ledger, exam permits, retry windows, Askium launch orchestration, webhook result intake, certificate issuance, public verification, JWKS, and share-image output.
Operations layer: Filament admin resources, runtime settings, social provider toggles, payment provider switching, Mailjet-backed inbound support, blog management, and audit-oriented history tables.
Engineering roles
DevCerts is not just a public marketing page for certificates. It is a product layer where payment-domain records, voucher accounting, external exam delivery, result validation, certificate templates, public verification, admin workflows, and editorial SEO all have to stay consistent: the same shape of complexity found in many custom B2B development projects.
Backend language
Backend runtime for certification catalog logic, voucher operations, launch orchestration, certificate issuance, and public verification flows.
Application framework
Main framework for routing, authentication, payments, admin tooling, queues, webhooks, certificate rendering, and public pages.
Admin backoffice
Administration layer for certification exams, users, vouchers, permits, companies, payments, certificates, blog content, settings, and health widgets.
Database
Relational storage for users, vouchers, ledger entries, certification exams, permits, attempts, certificates, companies, payments, and blog content.
Cache and queues
Infrastructure layer for cache, background jobs, payment and mail workflows, and operational work that should not block user-facing screens.
Server-driven UI bridge
Connects Laravel routes to Vue application screens for candidate workspace flows without a separate API-first frontend deployment.
Frontend interface
Interactive UI layer for dashboards, exam permits, profile settings, company access, voucher balance, and candidate certificate surfaces.
Workspace interaction language
Client-side language for candidate workspace interactions, voucher flows, profile and security screens, and public certificate surfaces.
Build pipeline
Frontend asset pipeline for the public site, authenticated workspace, admin-adjacent screens, and production bundles.
UI styling system
Utility CSS system for public pages, certificate templates, candidate workspace screens, blog views, and dense operational UI.
Social authorization
Authorization protocol behind social sign-in connections, profile identity linking, and provider-managed authentication flows.
Certificate render runtime
Runtime used by the certificate PDF and share-image rendering toolchain through browser automation dependencies.
PDF and image rendering
Headless browser rendering stack for certificate PDFs, preview HTML, public share images, and credential presentation assets.
Regression coverage
Regression test stack for certification domain rules, payments, webhooks, candidate flows, public verification, and admin behavior.
Start with a conversation
Talk through a platform that connects accounts, payments and external services into a clear customer journey.
