How certification works
From the open catalog to the credential another person can verify. At each step, what you do and what the server requires for the step to count.
Lessons, checks and practice tests are free; the exam and the credential are paid, once per credential. The account is there to save progress and take exams — the catalog and credential verification are public.
What is not ready yet
- The whole program is in Preview, as the platform. Each lesson shows the state badge of the capability it teaches and nothing here is announced as generally available.
- The pedagogical review of the question banks is a pending human gate: the questions are written and anchored in the documentation, but the formal review of the curriculum and of the question banks has not yet been signed. Meanwhile, content opens in batches.
- Recertification is designed (a short exam at the end of validity) and hasn't opened yet — no credential has come close to expiring, and its price isn't set.
- The validation page for code or fingerprint (/academy/validar) is going live. Until it responds, the credential link itself already verifies — it's the same source of truth.
- The new design of the credentials — with ICSA as the final stage above the others — has been decided, and the published catalog is being updated for it. Until then, each credential's pages show the requirements of the previous version.
Six steps, with both sides in view
The left column is what you do. The right one is what the server requires — it is what makes the credential defensible to anyone who checks.
Open catalog
You open tracks, courses and lessons without an account and without a card. The requirements and the price of each credential are on its own page — you can see everything before deciding.
What the server requires
- The catalog pages are static and do not consult session: no one is sent to login to read a lesson.
- The catalog is validated when the site is generated. A broken reference prevents publication — the page never goes out half-finished.
- What requires an account is only progress, the exam and challenge submission.
Lesson with check
You watch (or read) the lesson and answer a quick check of 2 to 3 questions at the end.
What the server requires
- Correction runs on the server. Correct answers and explanations are not sent to the browser before you answer.
- With a published check, the lesson only counts as completed from 70% correct. You can repeat as much as you want; the best score counts.
- A lesson whose check hasn't been written yet still completes normally — the content isn't hostage to a quiz that doesn't exist.
Course completed
You finish the lessons in the track order and follow the progress bar in “My progress”.
What the server requires
- Progress counts only the lessons that exist in the catalog: a renamed or removed lesson does not inflate your percentage.
- A course without a published lesson never appears as completed.
- Progress belongs to the person, not the company: it does not depend on workspace, plan or invitation.
Practical challenge and exam
You build the requested artifact in your own workspace, export and send it; then accept the honor code and take the exam.
What the server requires
- Before opening the exam: required courses completed, the challenge approved and a valid entry badge. If something is missing, the list says exactly what is missing.
- The challenge is graded assertion by assertion on the file you sent. An assertion the grader does not recognize fails — nothing passes by omission.
- The exam is drawn by domain at the moment you start and is stored as you saw it, so the grading uses exactly that form.
Name consent
You write the name as you want it to appear on the certificate and choose whether it is visible on the public page.
What the server requires
- Without this consent the credential is not issued — and nothing is lost: the approval is stored and issuance unlocks when you fill it out.
- The name stays only in our database. The signed credential file does not carry a name; the email is included only as a hash.
- Those who prefer not to publish their name receive the same credential: the page shows the valid code without identifying the person.
Verifiable credential
You receive a code, a public page with a QR, a fingerprint to check on paper and a signed file to attach on LinkedIn or send to a client.
What the server requires
- The credential is digitally signed in the open badge standard (Open Badges 3.0), and the public key is published for anyone to verify.
- The public page is the source of truth: if the credential was revoked or expired, that's what it says, even if the signed file is intact.
- A signature we cannot verify appears as “not verifiable”, never as valid.
An entry badge and 4 certifications
Each row comes from the catalog: the number of questions, the time, the cutoff score and the question bank size are the same the exam uses. The practical challenge is mandatory along with the exam.
| Credential | For whom | Questions | Time | Cutoff score | Bank | Practical challenge |
|---|---|---|---|---|---|---|
| ICFFundamentos IngestiaIngestia Certified FundamentalsBadge | Todas as pessoas que vão usar a plataforma: quem decide, quem analisa, quem implanta. É a base da pirâmide — vem antes de ICED — Engenheiro(a) de Dados, ICBI — Analista de BI e ICIA — Engenheiro(a) de Agentes de IA, que por sua vez vêm antes do capstone ICSA — Arquiteto(a) de Soluções. É o vocabulário comum — os seis produtos do menu, os selos de estado (Preview, GA-candidato, Roadmap), os cinco papéis, o medalhão Bronze/Silver/Gold, como compartilhar sem vazar e como o custo é guardado. | 30 | 45 min | 70% | 120 questions5 domains |
|
| ICEDEngenheiro(a) de Dados IngestiaIngestia Certified Data EngineerCertification | TI, implantadores, consultores e parceiros que conectam ERP, bancos e arquivos, cuidam de credencial, agenda, qualidade e custo de ingestão, e entregam o datalake pronto para quem analisa.Requires: ICF | 55 | 100 min | 72% | 200 questions6 domains |
|
| ICBIAnalista de BI IngestiaIngestia Certified BI AnalystCertification | Analistas de BI e controladoria, quem já usa Power BI ou Excel, e quem vai ser o criador de painéis da empresa. Se você vem do Power BI, a rota rápida leva à mesma certificação com menos aulas (teste de dispensa por aula).Requires: ICF | 60 | 110 min | 72% | 220 questions5 domains |
|
| ICIAEngenheiro(a) de Agentes de IA IngestiaIngestia Certified AI Agent EngineerCertification | Analistas avançados, TI e a pessoa que vai ser a referência ("champion") de IA na empresa: quem configura orçamento, decide o que pode sair para o modelo, monta os relatórios do Analista de IA, publica agentes e fluxos, e audita o que a IA respondeu ou executou.Requires: ICF | 50 | 90 min | 72% | 180 questions6 domains |
|
| ICSAArquiteto(a) de Soluções IngestiaIngestia Certified Solutions ArchitectFinal stage | Quem responde pela solução inteira, não por uma camada dela: líder técnico de implantação, consultor que assina a proposta, parceiro com portfólio multi-CNPJ, e a pessoa de TI que vai ser a referência do ingestia.io dentro da empresa.Requires: ICF + ICED + ICBI + ICIA | 50 | 110 min | 75% | 200 questions6 domains |
|
Validity of 1 year for all. The name in Portuguese appears in the interface and on the certificate; the English alias is recorded in the credential, for those who need it outside Brazil.
The badge at the base, the roles in the middle, the entire solution at the top
ICSA is not “just another”: it is the final stage, which only opens to people who have proven each layer below. It separates those who master one part from those who are responsible for the entire solution.
Drag the diagram to the side to see the full credentials.
Base
ICF — Fundamentos IngestiaPrerequisite of all others. It's the common vocabulary: the journey from source to decision, the state badges, the access roles and the data layers.
The paper certifications
- ICED — Engenheiro(a) de Dados Ingestiamodule Ingestia Data
- ICBI — Analista de BI Ingestiamodule ingestia.bi
- ICIA — Engenheiro(a) de Agentes de IA Ingestiamodule Ingestia AI
One per product layer. Each requires a valid entry badge, its exam and its practical challenge.
Final stage
ICSA — Arquiteto(a) de Soluções IngestiaRequires ICF and the 3 valid paper certifications: ICED, ICBI, ICIA. The exam is mostly scenario-based, and the challenge asks for an end-to-end solution — not a piece of it.
How the exam defends itself without a proctor
There is no proctoring, webcam, or software watching your machine. What supports the result is the exam design — and each item below is implemented, not planned.
Randomization by domain
Each exam is assembled on the spot, taking from each domain the quota the blueprint specifies. The bank has at least double the quota of questions in each domain, so two people almost never see the same exam — and the order of alternatives is also randomized.
Server clock
The deadline is recorded when the attempt starts and is not recalculated later. The browser only displays the time; closing the tab, switching machines, or changing the computer clock does not buy you a minute.
Server-side correction
The grade never comes from the browser. The exam you answered is stored exactly as you saw it, and the correction runs on that copy — even if the question bank changes later.
Feedback by domain, no answer key
The result says how many you got right in each domain and what to review. It does not say which question you missed nor what the correct answer was: the question bank is reused and the answer key cannot leak.
Wait between attempts
Failed the entry badge: 24 hours, then 7 days, then 30 days. Failed a certification: 14 days, and at most 3 attempts per 12-month window. There is no retry until you pass by repetition.
Abandonment counts as an attempt
An attempt started and not submitted by the deadline (one extra minute for the network) counts as a failure. Closing the tab does not reset an exam that was going poorly.
Honor code, not camera
There is no proctor, no webcam, and no software watching your machine. You accept a versioned honor code before starting; the exam is defended by the design above, not by surveillance.
No capability that doesn't exist
The exam only assesses operation of what the platform does today. A capability marked as Roadmap or blocked can only be asked as a state (“does this already exist?”), never as a task.
The credential is a public address, not a PDF
Anyone who receives the link checks it by themselves, without asking us and without a platform account.
Four ways to verify
- By the code: 14 readable characters, no information about the holder. Opens the credential's public page.
- By the QR: the same page, printed on the certificate — a phone camera reads it.
- By the fingerprint: a cryptographic summary of the signed file, in 8 groups of 4 characters. Whoever received a printed paper or a screenshot copies those 32 characters and verifies — without depending on clicking any link.
- By the signed file: the credential in the Open Badges 3.0 open standard, digitally signed. The public key is published, so any compatible tool can verify the signature without checking with us.
For the code and fingerprint there's a page just for that: /academy/validar. Paste what you have and it returns valid, expired or revoked.
Validity, expiration and revocation
- Validity of 1 year. The product changes fast; a credential without an expiration would become false over time. Once expired, the page shows “expired” — it doesn't disappear.
- Recertification by short test, at the end of validity, by a short delta exam. It's designed and hasn't opened yet — the price included.
- Revocation overrides signature. The public page is the source of truth: if we revoke, that's what it says, even if the signed file remains intact.
- Account closed: the credential is anonymized and revoked, and the page keeps responding. A "does not exist" would tell an employer that the credential was never issued — and that would be false.
The holder's name only appears with explicit consent, given at issuance, and can remain hidden: the page then shows the valid code without identifying the person. The signed file never carries a name, and the email appears only as a hash.
What is free and what is paid
Lessons, videos, checks and practice tests are free: no card, no plan. The exam and the credential are paid, once per credential — from R$ 200,00 to R$ 950,00, and each credential's price is on its own page. The free account (email or Google) saves your progress. The catalog and credential verification are public: whoever receives your link doesn't need an account.
The practical challenge runs in your own workspace and grading is deterministic on our server, without querying an AI model — that's why studying generates no cloud cost for either side.