goca

Architect training

Access on request.

The Architect module is the deployment-design material: the issuance split, what co-locating roles gives up, custody strategy per CA, the database as load-bearing state, scaling, multi-region — and which parts are designed but not built. It sits behind a password because it is written for people who design PKI deployments for a living, and because we want to hear back from the people reading it.

Who it is for

Consultants and engineers who implement PKI for customers — people who have run AD CS, EJBCA, Dogtag, Vault PKI or something like them, and who can tell us where goca falls short. That is not a gate on job titles; it is a description of who the material is written for.

The deal, stated plainly

We give you the gated Architect material. In exchange, you publish something public that mentions goca (go-ca.org) — a post, a note on your own site, a write-up, a talk. That is an exchange, so both sides say so: we say it here, and we ask you to say in your post that we gave you access to the gated material on that basis.

What you write is yours. We do not review it, we do not approve it, and we ask for no particular tone — a critical write-up counts exactly as much as a favourable one, and the criticism is frankly the more useful of the two. No money changes hands in either direction, and nothing here is a paid placement. If those terms do not suit you, that is a fair reason not to apply.

How access is granted

Send the form below — or talk it through with the assistant on the support page first, which asks the same questions and will summarize the conversation into something you can paste in here. We ask about your PKI background, whether you have deployed goca yourself, what you actually tested, and what you would improve. The last one is the point: substantive first-hand feedback is what this material is being traded for, and it is the field we read first.

A person reads every application and decides by hand. You get an answer by email either way. There is no queue to check, no automatic decision, and the assistant on the support page holds no code and cannot grant access.

Where we send the decision — and, if it is a yes, your access code.

Products and your role — consultant delivering for customers, in-house operator, or vendor.

Deployment shape, custody mode, ACME, templates, PQC algorithms, four-eyes approval, audit verification. “Not yet” is an honest answer.

What was confusing, missing or broken. Be blunt — this is the field we read first, and blunt is what it is for.

Your own site, a blog, LinkedIn, X, a conference talk — wherever you normally write. We ask that the post mentions you were given access; we ask nothing about what it says.

Already have a code? Paste it into the password field on the architect sign-in page. The Operator training is open to everyone with no code at all: start there.