A demonstration is the reference deployment brought up live and walked in front of you: on a laptop with no network, or on a network of yours. Bring the questions your security team asks first.
Say who you are and what you run, and a demonstration is arranged around it. Three things make the first reply a useful one:
Licensing, deployment, support, or a capability you do not see on the evidence register. A short note is enough, and the answer comes from the people who ship it.
If you would rather read first, the documentation is public and the evidence register names, capability by capability, what proves each claim on the home.
AuthBox is source available: source to a licensee on request, images to anybody. The AuthBox team develops it and grants every license over it.
One server, by itself, with people to log in as, in one line: docker run -p 8443:8443 -p 8080:8080 authboxus/authbox-eval -evaluate.
Evaluation is free for everybody. authboxus/authbox and its companions are on Docker Hub beside it, all free to pull on these same terms. Point your scanners at them, run a proof of concept, evaluate it for a procurement. No key, no registration, no time limit, and the same for a public agency and its contractors.
A hundred enrolled people on a box that stands alone, or twenty-five across a federation of up to four boxes, for your own people and systems: no fee, no key, no support.
Only the people the box is the authority for count, the ones it issued a certificate or credential of its own. People who arrive through your corporate directory or single sign-on and pass through a door are not counted, so fronting a cluster or a service costs nothing at any size, and neither do machines, services or doors. The box shows the count on its console.
More people enrolled, a larger federation, or the product offered to others as a service: a commercial license from the AuthBox team.
An enterprise license comes with people: deployment, integration with the directory and PKI you already run, operations and support, from the AuthBox team and the partners we work with.
The terms are one page, in plain words, and the page the site carries is rendered from the license file the repository and every release ship. authboxjs, the browser SDK an application embeds to talk to the door, is Apache-2.0 on its own, so your application's code owes nothing to the product's license.
We're proud of our connection with Omnyon, rooted in our founder's professional relationship with the company. It is a relationship we value and look forward to building on as AuthBox grows, and we are excited to explore collaboration that draws on our respective strengths: independent product innovation on one side, and the people and expertise to meet complex technical challenges on the other.
AuthBox is an independent product, developed and licensed by the AuthBox team. Every evaluation, sale, license and support request is handled directly by us.
A certificate says who you are and a mission says why you are here; the same sign-in reaches a web application, a shell and an API through one door.
An operation nobody declared, asked for by someone who looks entitled, and the signed record that says exactly why it was denied.
The evidence register open next to the running system, so a claim on the home can be followed to the test that proves it.
Rather start on your own? The getting-started series starts from one docker run on a laptop, and the home links down to every shape it describes.
AuthBox