Private source delivery
The client receives the source code for their system. It is private: the rights to use it are defined in the contract.
Four capability areas we can take from design to production. Each is scoped per project — we define what we build, where it applies, and how the scope is agreed, before any code is written.
Capability statements: these describe what AIGU can build when a project requires it. Where we refer to systems we have already built, they are linked to Our Work.
AIGU can design and implement end-to-end encryption for data flows that fit your project's requirements — for example, private messaging, secure document exchange, or records that must stay unreadable to the server operator.
With E2EE, data is encrypted on the device that sends it and only decrypted on the device that is meant to read it. The servers in between carry ciphertext only. Key management — how keys are generated, stored, rotated and revoked — is part of the architecture we design with you.
TLS (HTTPS) protects data in transit between the device and the server. Encryption at rest protects stored data. E2EE protects the data itself, so that not even the server operator can read it. The three are different layers and can work together — we design them as layers, and we never use one term to mean another.
Optional defined zone: server-side AI reads plaintext only inside a boundary that the design states — who, what, and for how long.
Whether E2EE applies depends on the data flow and the product's requirements. It is an architecture we can build when the project calls for it — it is not a default claim across all AIGU products.
AIGU can build the real-time layer of a product: chat, live status updates, instant notifications, data synchronisation and multi-user collaboration.
One of our in-house web apps runs real-time production data from a factory floor — machine sensors, stop-line alerts and live output, viewable on mobile. See Our Work → Custom systems. See Our Work →
The real-time scope — which features, which transports, which environments — is defined with you and agreed in the contract.
AIGU can design and implement security for applications that serve end users directly — with accounts, personal data and multiple access groups.
These are implementation capabilities we can deliver per project. They are not existing certifications or audit results: AIGU does not claim ISO 27001, SOC 2 or independent penetration-test reports.
The security scope — threat model, controls and deployment target — is defined with you and agreed in the contract.
AIGU can develop software with a defined delivery mechanism: source code, technical documentation, deployment guides and operational transfer, under contract.
The client receives the source code for their system. It is private: the rights to use it are defined in the contract.
Ownership and licensing are contractual terms we define clearly before the build starts.
We use open-source libraries where appropriate, with their licence terms respected and documented.
Releasing a project under an open-source licence is a separate option we can agree. Receiving source code does not make software 'open source'.
Which of these applies to a project is a contractual decision we make with the client — we describe the options, the client chooses.
Bring us the problem — private data, real-time collaboration, or a system you want the source of. We'll scope it with you.