One repository. Everything we ship, readable.
AWA is a complete web software foundation — framework, office documents, cryptography, tooling, serving — developed in a single monorepo by a single team. Nothing downloaded from a public registry runs in our products. What runs is what you can read.
Developers ↗ — the code and its documentation on awaforge.euWhat does AWA contain?
| Layer | What it does | Licence | Maturity |
|---|---|---|---|
| Framework | Browser framework written from scratch: components, dependency injection, routing, dev server. Plain JavaScript modules, no bundler required | Apache-2.0 | L3 |
| Cryptography | Cryptographic primitives written in-house, in the same repository, compiled to WebAssembly | Apache-2.0 | L3 |
| Office documents | Read and write PDF, Word/Excel/PowerPoint, OpenDocument and Markdown in the browser; PAdES signatures; conversion to structured Markdown for AI pipelines | AGPL-3.0 or commercial | L4 (reference) |
| Tooling | Build, code generation, SBOM, licence stamping, export and verification pipeline | Apache-2.0 | L1–L2 |
| Serving | Our own static hosting, TLS edge and supervisor — this site runs on it | — | L1 |
Maturity is declared in the code of every package, on a scale from L0 (draft) to L4 (reference), and is never lowered. We only make commercial claims on what the level supports.
What can you verify yourself?
- Zero external runtime dependency. Open any package manifest: the only entries are other AWA packages from the same repository.
- Supply chain under control. The rare third-party code (in cryptography) is committed in the repository with its provenance and licence, pinned by hash.
- Air-gap deployable. No registry, no bundler, no telemetry, no call home. An isolated network changes nothing.
- Controlled releases. Public releases will leave from an isolated, verified copy of the repository, with signed tags and an SBOM attached — the list of every software component inside a release.
How is it built?
Every change goes through written plans, automated tests (unit, integration, cross-package), coverage gates and conformance reviews. Our production system — including the AI-assisted part — is versioned in the repository like the code itself: every task leaves a report stating who did what and how it was verified. Structural decisions stay human.
Where do you go next?
- Developers: awaforge.eu — docs, licensing, changelog.
- Compliance: what the code proves, framework by framework.
- Offers: licences, OEM, the Sovereign Guarantee.