Build with encrypted data.
Build applications with client-side encryption and live synchronization. Work with JSON on your devices; store encrypted resources on your server.
Choose your starting point
Work with JSON. Encrypt and synchronize on the client.
Get startedCreate witnesses and verify how a state advances.
Get startedStore encrypted resources on your own infrastructure.
Get startedHow the pieces fit
The SDK encrypts your data. The server checks witness transitions, stores accepted updates and notifies subscribed clients. Those clients verify and decrypt the changes locally.
The SDK manages Core chains internally, so you can start with the JSON data API. Need a compatible endpoint? Run the local server.
What stays on the client
Passwords, encryption keys and private origins stay on the client. The server sees IDs, witnesses, ciphertext and traffic metadata. It checks chain progression; it cannot decrypt the data or verify its AES-GCM tag.
ULDA does not provide an account directory or password-reset service. Your application and deployment supply their own account experience and access controls.
Source and licenses
Each component has its own repository, releases and license.
| Product | Source | License |
|---|---|---|
| Auth SDK | ulda-auth | SDK license |
| Core | ulda-core | Core license |
| Server | ulda-server | Server license |