Question
What are the three main products in the Noumena platform stack, and what does each do?
Answer
NPL & Runtime is the core engine for building event-driven business applications; Noumena Cloud is a pay-as-you-go hosting offering; Noumena Pulse is a mid-layer that connects those apps to blockchains.
Noumena Digital (a Swiss deep-tech company in Zug) ships three layers that build on each other:
- NOUMENA NPL & Runtime — the core. NPL (Noumena Protocol Language) is the language you write business logic in, and the Runtime (also called the Engine) executes it: managing state, permissions, events, and scheduling.
- Noumena Cloud — a secure, pay-as-you-go hosting offering, ideal for proofs-of-concept and minimum-viable-products that need to be validated quickly without running your own infrastructure.
- Noumena Pulse — a mid-layer for blockchain integration: wallet abstraction, smart-contract abstraction, and connectors that let a Runtime application issue and manage tokenised financial assets across many chains.
The theme across all three is modular, event-driven applications — especially tokenisation and regulated financial workflows.
Go deeper:
What is NPL (Noumena documentation) — the vendor's own introduction to NPL and the Runtime, showing how authorization is baked into the language and compiler.
Note saved — thanks!
Question
In NPL (Noumena Protocol Language), what is a "protocol", and why is it the central object?
Answer
A protocol is the core business-logic object: a stateful agreement between parties that bundles together its data, its allowed actions, and who may perform them.
Rather than scattering business rules across services, NPL packages them into a protocol — think of it as a smart contract for a workflow (a rent contract, a stablecoin issuance, a credit check). A protocol carries:
- State — where the workflow currently is (e.g.
requested,verified,rejected), advanced by explicit state transitions. - Parties — the entities allowed to interact with it.
- Permissions and obligations — the actions those parties can or must take, gated by the current state and by authorization.
Because state, actions, and access all live in one place, the Runtime can enforce them atomically and produce a clear, auditable trace of everything that happened — which is exactly what regulated financial workflows need.
Go deeper:
Protocols (Noumena documentation) — how a protocol bundles states, fields, permissions, obligations, and parties into one executable agreement.
Note saved — thanks!