Three certificates. One fabric.

Training for the people who design applications, the people who run the cluster, and the people who decide how the two fit together. Each course ends with a practical assessment. The certificate names the person, the track and the date.

Application developer

Designs an application and deploys it.


  • Studio. Modules, ports, connections and volumes, drawn so the plan can be read before anything runs.
  • Change. A new version, a stopped module, and what the review says will happen.
  • Limits. Which modules can deploy today, and which are still catalog entries.
Ask about this track

Application administrator

Keeps a running fabric healthy.


  • Fabric Console. Servers, health, alerts, backups, roles, tokens and the audit log.
  • A failed server. What restarts on its own, what waits, and how a person confirms a server is off.
  • Access. Who may deploy, who may change the cluster, and what is written down afterwards.
Ask about this track

Apelora architect

Both layers

Decides how applications and the cluster fit.


  • Placement and storage. Replicas, shared disks, and what happens when a server dies.
  • Identity and sites. Roles, and which multi-site ideas are written down but not built.
  • A review. A design checked against what the lab has proved, with the gaps named.
Ask about this track

How you earn one

The same three steps for every track. Length and format are agreed in the quote. The software itself stays free.

  1. The course

    Taught on a lab cluster, using Studio or the Fabric Console for that track. The architect course uses both.

  2. The assessment

    A practical task: deploy a small application, recover from a failed server, or review a design and name what is not built yet.

  3. The certificate

    It names you, the track and the date. It is not a licence to operate someone else’s cluster, and it does not expire on a timer we have not published.

What the certificate means

It records that you completed that course and that assessment. It does not say the product is ready for production on your servers.

It says

  • Which of the three tracks you completed
  • The date of the assessment
  • That the work was done on a lab, with the current software

It does not say

  • That a public exam is open, or that a price is published
  • That an outside body accredited the certificate
  • That every module, or a physical server, was part of the assessment

Tell us about your environment

How many servers, what storage and network, who needs access. We will tell you what Apelora does for that today and what it does not.