About Badges Ninja — issue verifiable Open Badges

Who runs it

Badges Ninja is built and operated by the team at Blockchain Web Services (BWS), with Nacho Coll as founder and engineer. BWS is an AI-native solutions factory that ships production-ready software across a portfolio of products — Badges Ninja is one of them, alongside OpenAgile.AI, Zellbox, WallaWhats, IPFS.NINJA, Blockchain Database, NFT.zK, and Telegram XBot. The operating principle is Demand Becomes Product: engineered by people, accelerated by AI, accountable end-to-end — every line of code owned by a named engineer.

The founding team has been building on AWS since 2007 (Enterprise Architect work for LEGO, Nordea, Vueling and others) and on blockchain / decentralized-storage infrastructure since 2019. Badges Ninja launched in 2026 because the credentialing tools we evaluated for client work were all enterprise-gated — custom pricing, no self-service sign-up, and weeks of onboarding just to issue a first badge — when the underlying Open Badges spec is an open standard anyone should be able to use.

What we make

Badges Ninja lets you design a badge or certificate, define its criteria, and award it to recipients as an Open Badge v2.0 credential. Every award is verifiable: it carries baked-in metadata about the issuer, the achievement, and the criteria, so anyone can confirm it is genuine on a hosted verification page — no phone call to the issuer required. Badges are interoperable with any platform that supports the standard, including LinkedIn.

The API is intentionally minimal — create an issuer, define a badge class, award it — and there is a visual designer for teams who would rather not touch code. A recipient portal, hosted public verification pages, and IPFS-backed image hosting come in the box. A free tier lets you issue real credentials before paying anything, with paid Starter ($9/mo) and Pro ($29/mo) plans as you grow.

Why it exists

Most credentialing platforms are built for large enterprises: custom pricing, no self-service sign-up, and weeks of onboarding to issue your first badge. Yet the underlying spec — Open Badges — is an open standard anyone should be able to use. Badges Ninja exists to be the fast, honest, self-service way to issue standards-compliant credentials, priced so a single trainer, a conference, or a small certification body can start for free and only pay as they grow.

How we use AI in our content

Some blog posts on this site are drafted with the help of an AI assistant using a prompt that ranks topics by underserved search intent and drafts a code-first article body. The Badges Ninja team then reviews the draft, verifies every code example and price against the live product, corrects any factual errors, and approves publication. Articles that pass this review carry the byline “Nacho Coll” and include a disclosure note. Our full workflow is documented on the editorial process page.

We disclose this per Google’s helpful-content guidance, which asks that appropriate use of AI generation is self-evident to visitors through disclosures. We agree.

Editorial standards

We don’t accept paid placements, sponsored posts, or affiliate links. Comparison articles (e.g. “Badges Ninja vs Credly”) are written with explicit prices and feature counts taken from the competitor’s public documentation, and we link to their site so readers can verify the facts themselves. If you spot an inaccuracy in any post, email support@badges.ninja — we’ll correct it and add an editorial note.

Reach us

Product — badges.ninja
Email — support@badges.ninja
Author — Nacho Coll
Editorial process — how we make this blog