9 Months to Deliver

What we do and why

In aviation, an expired training certificate can ground a pilot. A missing qualification can delay a flight by hours. And today, verifying these documents still relies on phone calls, emails, and Excel files shared between organizations that don't talk to each other.

Kepler Aviation is building AeroCert to solve this problem. AeroCert leverages an API-based blockchain to enhance traceability, trust, and compliance in aviation certification data. Every certificate issued is recorded on this ledger: timestamped, tamper-proof, and instantly verifiable by any authorized party — an employer, a regulator, a training organization. The certificate's status is immediately available: valid, expired, revoked, or absent. The answer takes less than a second.

What makes AeroCert different is not "putting a certificate on a blockchain" for the headline. It is turning blockchain into a compliance infrastructure accessible by API: organizations keep working in their own tools, but every important certificate becomes a verifiable, interoperable proof that an authorized third party can use. In a market as regulated as aviation, this combination — business API, tamper-proof ledger, compliance proof — changes how certificates circulate.

The AVIA token, from the Kepler Digitals ecosystem, will be progressively integrated into AeroCert to secure transactions and cover the platform's gas fees. Its role is operational, rooted in actual product usage. Growth in AVIA usage volume must be a consequence of AeroCert's rollout: the more certificates are tokenized, the more operational network needs increase. The order is deliberate: product first, usage next, token as a consequence.

What you're reading is our roadmap for the next 9 months. We will only publish what has been shipped. No teasing, no "coming soon," no projections without foundation. Every month below corresponds to a verifiable milestone. If we miss one, we'll say so too.

---

April 2026 — Laying the foundations

Until now, AeroCert ran on a testnet — a test environment isolated from the real world. This month, we switch to mainnet. This is the moment the platform stops being a prototype and becomes a product in production.

Concretely, this means MBAviation — a major player in aviation training and airport operations, and our first strategic partner — will begin using AeroCert's APIs in production through its MBAClarity application. The operational goal is to be able to process up to 5,000 diplomas and certificates per month with MBAviation, then grow that volume progressively in 2027. These are real documents for real aviation professionals.

The aerocert.co website will be refreshed alongside. The goal: make AeroCert's value proposition clear — a verification system built on an API-based blockchain that enhances traceability and trust in certification data. Clean, sober positioning centered on what the product actually solves.

On the investor side, this is the moment for the first factual communication — a status report on AeroCert as it stands now, not an abstract promise. To date, the product represents 705 commits and roughly 179,000 lines of source code excluding lockfiles and generated files. The existing building blocks cover certificate issuance, blockchain anchoring, public verification, document templates, batches, the SDK/API, webhooks, OCR, managed wallets, and approval workflows. The communication starts there: what exists, what moves into production, and what still needs to be secured.

In parallel, advanced discussions are underway with two players in the aviation training and ground handling sector, candidates to join the AeroCert ecosystem. In April, these discussions reach their decision point.

May 2026 — The first proof that can't be ignored

May is the month when the proof goes public, on two fronts.

First, the first certificates issued through MBAviation will be effectively recorded on the blockchain — anyone will be able to verify their existence and validity through a minimal public dashboard. This dashboard will show the issuing organization, the validity of the information present on the certificate, and the comparison with the blockchain fingerprint. The whole flow remains GDPR-friendly: no personal information is published in clear text on-chain, and unnecessary copies of sensitive clear-text data are avoided on the server side.

Then, the field. A first POC launches in a West African country with a local training organization, based on a signed commercial engagement. Altéa training sessions — CM and FM refresh, in virtual classroom format — take place mid-May, and it's within this window that AeroCert must demonstrate real-world tokenization of certificates. This is the first full-scale test outside Europe, on a continent where aviation certification is a massive need and verification infrastructure remains highly fragmented.

It's also the month when token visibility must be restored on standard platforms. The crypto environment has been challenging — prolonged bear market, war on Europe's doorstep, instability in the Middle East, regulatory uncertainty, and a US presidency casting doubt on global financial markets. Like many project tokens, the listing has lost visibility on platforms such as CoinGecko and common wallets. Restoring this visibility is a priority technical effort in May, because it's a credibility prerequisite for every communication that follows.

Starting in May, a written monthly update will be sent to investors. Always the same format, always factual: here's what was done, here's what's next.

June 2026 — Industrializing the building block

In June, AeroCert must prove it works beyond a single partner. Version 1.1 ships with a documented public API — meaning any training organization can technically integrate on its own. A first client SDK is delivered, and an internal security audit verifies that what we've built holds up before opening it wider.

MBAviation is an ecosystem in itself — with dozens of partner training organizations across multiple countries. The goal in June is to activate new organizations within this ecosystem and finalize the integration of at least one external player. That's the difference between a product that works for a partner and a product that works for a market.

On the investor side, June is the month of the first written quarterly report. Three pages maximum: what was delivered, AeroCert metrics, and next quarter's roadmap. No "price outlook," no financial projections. An honest product review.

The engineering team expands during this period to support product scale-up and the opening of the API to third-party integrations.

July 2026 — Capitalize and decide

July is a pivotal month. The first West African POC is behind us, production data is accumulating, and the second POC file is being structured. This is not about announcing a date that does not exist yet: this file comes after the Africa wave. The use case itself is clear — centralizing ALTEA certificates on behalf of a network of ground handling organizations — and July is about turning that use case into product, commercial, and operational framing.

It's also the moment for a token decision that cannot be made in April based on assumptions. At this point, we'll have three months of AeroCert production data. Enough to see whether the product gains traction or not:

Either the token keeps its current role — covering gas fees, with no broader usage mechanism. We keep advancing the product, and trust rebuilds through proof.

Or we take a step forward and define a concrete utility. The working hypothesis is simple: an organization holding AVIA gets a 10% discount on its AeroCert tokenization fees. Payment stays in euros, but holding the token unlocks a measurable pricing advantage. This path is more ambitious but requires serious legal work — token qualification, MiCA compliance, specialized lawyers — that must start in July to be operational by October.

We will only make this decision in July, based on what the data shows. Not on what we hope.

In parallel, an external security audit of AeroCert begins to prepare the transition to SaaS.

August 2026 — Stress-testing before opening

August is the closed beta month. We invite 5 to 10 pilot schools to use AeroCert SaaS under real conditions. The goal is not to sell — it's to break the product before real clients do. How many certificates per day before things slow down? What happens when 10 organizations create certificates simultaneously? Where are the friction points in onboarding?

If July's decision opened the path to expanded utility, the legal work and technical specifications progress alongside the beta. The two workstreams are independent but converge toward the same objective: a clean launch in September.

A quarterly status update brings together a core group of investors for a direct conversation on progress.

September 2026 — Preparing the public launch

September is the month when we prepare the public opening. AeroCert SaaS moves out of closed beta and into release candidate: the first organizations create their account, configure their space, and test the issuance and verification journeys. There will still be manual support, and that is normal at this stage. The benefit is not to remove every human intervention on day one; it is to make blockchain access simple for an organization with no Web3 team, no wallet to manage, and no smart contract to understand.

Pricing is locked in euros. If the utility path was retained in July, the pricing advantage rules linked to AVIA holding — including the target 10% discount on tokenization fees — are documented, legally validated, and prepared for a controlled commercial launch. Nobody is forced into it, and payment remains in euros.

September is also about moving beyond API-only usage. AeroCert must be usable in two ways: directly through the API from partner tools, or through the AeroCert interface for organizations that want to issue and verify without heavy technical integration. The onboarding documentation and product communication must make both paths clear.

The goal in September is not yet to maximize the number of registered organizations. The goal is to lock the funnel: sign-up, configuration, issuance, verification, invoicing. If that chain is smooth, October can become a real commercial month.

October 2026 — Commercial launch and traction

October is the commercial launch. We target flight schools, ALTEA-certified organizations, airline training centers. The public measurable goal is deliberately simple: 5 organizations registered on the platform and able to test a full journey, from issuance to verification. At this stage, the priority is to validate interest, objections, onboarding time, and the quality of the commercial pipeline.

If the expanded utility has launched, October is mainly about observing the first signals. Do some organizations understand the value of holding AVIA to benefit from the 10% discount on tokenization fees? Does the topic create commercial value or friction? What volume of certificates actually goes through AeroCert? We will not turn curiosity into an adoption promise. The only acceptable trajectory remains the product trajectory: AeroCert usage first, AVIA usage next.

The Q3 quarterly report will cover these numbers without filters.

November 2026 — Accelerating commercial actions

In November, the topic is no longer only proving that the product works. The topic becomes commercial: turning the first uses into a structured pipeline. We expand what AeroCert can certify — pilot licenses, endorsements, currency checks, ratings — so we do not remain locked into a single ALTEA use case.

This expansion directly serves commercial actions: flight schools, training organizations, training centers, ground handling players, airlines. Each segment must have a clear value proposition, a demonstrable use case, and a simple onboarding journey. We are not selling abstract blockchain technology; we are selling less friction, fewer manual checks, and lower non-compliance risk.

The goal is also to sign the first verification-side partner — an airline, employer, or authority that uses AeroCert to automatically verify a pilot's currency. When a verifying player connects AeroCert to its system, the commercial loop becomes much stronger: the training organization issues, the end customer verifies, and demand spreads naturally.

December 2026 — Measuring commercial traction

December is not a celebration month — it's a month of commercial truth. We put the numbers on the table: how many certificates issued by AeroCert, how many organizations registered, how many active organizations, how many paying organizations, what SaaS ARR, and what qualified pipeline for 2027.

We also measure actual adoption of the AVIA advantage if the utility path has been activated: how many organizations hold tokens to benefit from the discount, how many certificates are tokenized, and what operational usage volume this generates. Growth in AVIA volume must remain a consequence of AeroCert's rollout, not a promise detached from the product.

Based on these numbers — not intuition, not bets — we prepare the commercial actions for 2027. Maintain the current pace if signals are positive, focus effort on the segments that convert, suspend token activation if adoption isn't there, or accelerate if the numbers justify it.

Not before December. Never based on speculation.

Q1 2027 trajectory

A complementary opportunity is already taking shape for the first quarter of 2027. It is not part of the promises in this roadmap, because it will depend on what October to December actually demonstrate: pipeline quality, organizational maturity, certificate volume, and legal clarity around AVIA usage.

We therefore keep it in the right place: as a strategic option, not as an announcement. If it is confirmed, it will be communicated separately, with its own product, commercial, and regulatory framing.

---

Summary

---

Nine months is short. We don't promise everything will go as planned — we promise we'll say exactly where we stand at every step. The next letter will come out when there's something to tell.