Guide
Private deployment
Veylent runs in your own environment. This page is for the people deciding whether that’s practical: what’s involved, what you need, and what your IT team takes on.
What you run
| Component | What it does |
|---|---|
| Veylent server | Accounts and sign-in, saved signatures, and submitting signing records to the blockchain |
| Verification site | The page people reach when they scan a QR code, on your own domain |
| PostgreSQL database | Accounts, saved signatures, and the encrypted signer details |
The server and verification site ship as standard container images, so they run anywhere containers do: a single virtual machine, your Kubernetes or OpenShift cluster, or a private cloud. A ready-made Compose setup gets a first environment running quickly.
What you need
- A domain with HTTPS for the verification site, for example verify.yourcompany.com.
- An email (SMTP) service for sign-in codes. Your existing mail relay works.
- Access to a blockchain network through a provider or your own node, and a wallet with a small balance to pay network fees. The fee per signature is small, and your organisation pays it, not the signers.
- Optionally, Google or Microsoft sign-in, registered with your organisation’s accounts.
How a rollout goes
- Plan. Choose the domain, the blockchain network and the sign-in methods.
- Set up your signing contract. A one-time step that creates your organisation’s record on the blockchain, which only your server can write to.
- Start the services. The server applies its own database setup on first start.
- Roll out the desktop app, configured with your server’s address.
- Start signing. Anyone you send a signed document to can verify it straight away.
Day-to-day operation
- Health checks report whether the database and the blockchain connection are working, for your monitoring and load balancers.
- Upgrades replace the container images; database changes apply automatically and safely on start.
- Backups cover one PostgreSQL database. The signing records themselves are permanently on the blockchain.
- Scaling: run more server instances behind a load balancer as usage grows.
Choosing a blockchain network
By default Veylent uses Polygon, a widely used public network with low fees. A public network is what makes records verifiable by anyone, independently of your organisation. A private network is possible, but verifiers would then have to trust whoever runs it, which gives up much of the benefit. We recommend a public network unless you have a specific reason not to.