MAX
MAX
Mathematical Authorization eXchange

Who you are. What you can do. How you can prove it.

In the digital world, identity, signature, login, communication and devices are often separated. MAX tries to connect them through a common language.

It is not proprietary new cryptography and it does not promise absolute security. MAX uses known and studied components to connect identity, signatures, public keys, hashes, secure communication and devices inside a verification-oriented model.

The problem is simple

In the physical world, proving who you are is easy to understand: you show a document. In the digital world, instead, your identity is often split across accounts, passwords, signatures, chats, apps and devices that do not really speak the same language.

Each piece lives on its own

A username identifies you inside a service, a password lets you enter, a signature approves a document, a chat lets you communicate and a separate panel controls a device.

These tools are useful, but they often remain isolated. MAX was created to connect them inside a more coherent model.

For engineers and evaluators

The problem is not only authentication. The problem is integration between identity, authorization, signature, communication and device control. MAX tries to connect these layers through a common architecture, where identities, proofs, signatures, rules and reports can be observed and verified.

The MAX idea

MAX tries to connect who you are with what you can do, and to make that relationship provable.

Not only access. Proof.

MAX does not stop at access. It uses identity as a basis for signing, logging in, protecting data, communicating and authorizing actions.

The point is not to create another account. The point is to build a digital identity that can become a common basis for multiple functions.

A password opens a door. MAX tries to connect that door to an identity, a signature, a rule and a proof.

For engineers and evaluators

Technically, MAX connects local identity, identifiers, public keys, signatures, hashes, Merkle roots and post-quantum components. The server should not be seen as the owner of the identity, but as infrastructure that can transport, register or verify signed objects depending on the module.

Not based on the classic email + password model

In the most common digital model, identity starts from an account: you enter an email, choose a password and the server becomes the center of your access.

MAX starts from a different point

MAX does not base identity on the classic email + password + central account model. In MAX, identity is generated locally, on the user side or on the device side. The server does not need to know the personal secret and should not be the owner of the identity.

The server can transport requests, receive signed objects, verify proofs, distribute manifests or store reports, but it should not replace the source of the identity.

This changes the starting point: not “you have an account on a server”, but “you have an identity that can prove something”.

For engineers and evaluators

In the MAX model, personal secrets remain local and are not sent to the server. The server may see technical data required for operation, such as public identifiers, public keys, signatures, signed payloads, manifests, reports or operational metadata. In encrypted flows, the server can act as a relay or coordinator without reading the protected content.

This is why it is more accurate to say that the server is blind with respect to personal secrets and protected content, not that it is absent or magically invisible. The technically relevant separation is between local identity, verifiable proofs, supporting server infrastructure and protected content.

The three parts of MAX

MAX starts from mathematical research, becomes an app for people and extends to physical devices.

π
Mathematics

MAX Prime Theory

MAX Prime Theory is the independent mathematical research that inspired the MAX method, the idea of deterministic structure and the concept of an identity built in an ordered way.

It is not the operational cryptography of the system, it is not an encryption algorithm and it does not replace signatures, hashes or post-quantum components.

App
People

MAX App

MAX App is the human side of the ecosystem. It brings digital identity, signature, local vault, login and encrypted chat to iPhone.

It is not meant to be only a password manager or only a chat app, but a personal environment for identity, protection and verification.

IoT
Machines

MAX IoT

MAX IoT is the machine side. It extends the MAX model to physical devices, where identity, roles and rules must be verifiable.

The current prototype, tested on Raspberry Pi, demonstrates device identity, gateway and peer roles, signed Fleet Manifests, commands from MAX Chat, responses to the user and node alignment reports.

↔

From people to machines

The most important shift is continuity.

In the same model, a person can use identity, signature, login and communication. A machine can use identity, role, signed rules and reports.

MAX tries to bring people and devices into a platform readable through the same principles: who you are, what you can do, how you can prove it.

MAX App brings identity, signature and verification to people. MAX IoT brings identity, roles and verifiable rules to machines.

Built to be verified

MAX should not ask for blind trust. If something is important, it should leave evidence that technically competent people can inspect.

“Trust me” is not enough

A serious system should not merely claim that something is secure or authorized. It should produce controllable elements: a signature, a hash, a public key, a manifest, a report or a verifiable state.

For engineers and evaluators

MAX uses identities, signatures, hashes, Merkle roots, public keys, signed manifests, node reports and observable flows between app, server and devices. This does not mean that MAX is already audited or certified; it means that the architecture is designed to be analyzed, checked and improved.

What already exists

MAX is not only an idea. There is documented mathematical research, MAX App, Login with MAX, signature, vault and chat modules, an operational backend and a working MAX IoT prototype on Raspberry Pi.

The current phase is appropriate for an advanced independent project: working prototype, public clarification, documentation, technical validation and consolidation.

MAX is not yet an industrially certified product. Independent audit, external evaluation and scale testing remain necessary steps.

Login with MAX