Home/Deployment
Deployment
Confidentiality of the files and speed of onboarding are solved in different ways: our server for speed, your own server for confidentiality. Switching between environments takes one settings screen, and the clients do not need to be reinstalled.
Scenario A
You download the app or open the browser and sign up with your email. We create the organisation's space, invite the team and migrate the first case.
live on the day of your request · nothing to install
Scenario B
An Ubuntu server in the office or at a provider, or a Mac mini on the desk. The case files stay on your machine. We carry out the installation and hand over the system with training.
Ubuntu 22.04/24.04 and newer · macOS
Scenario C
Deployment in your perimeter with a model stack: commercial models under your control, a hybrid stack or a fully local stack. A separate contract with milestones and acceptance.
from 30 000 € · for firms with confidentiality requirements
Ubuntu
The installer sets up the dependencies itself, brings up the database and the queue, generates secrets, issues a TLS certificate for your domain, applies the schema, creates the first administrator and prints the address with the linking code.
If your team has no administrator, we will handle the installation and configuration — as part of our "turnkey deployment" service.
Ubuntu installation
# the domain's A record must already point to the server curl -fsSL https://cassation.app/install.sh \ | sudo bash -s -- \ --domain=delo.yourfirm.ua \ --admin-email=admin@yourfirm.ua # what the installer prints: # system address # linking code for the mobile apps # first administrator login # update bogatyr update
Mac
Inside is the same server, built for macOS. The services start when the system boots and are managed through a small window: start, stop, view the log, show the linking code, update.
Requirements
| Configuration | Minimum | Comfortable |
|---|---|---|
| Memory | 8 GB | 16 GB |
| Disk | 50 GB SSD | from 250 GB SSD |
| Processor | 4 cores | 6–8 cores |
| Local models | will not fit | 16–32 GB of memory |
A fully local environment needs spare memory for models — we will confirm the requirement during the pilot, based on the volume of your cases.
Connectivity
The most common obstacle: the server sits in the office behind a router without a public address, and the provider even shares one address across the whole building. You cannot ask a lawyer to configure a router — so the server itself establishes an outbound connection. Any router allows outbound traffic on 443.
| Path | When it works | What happens to the traffic |
|---|---|---|
| Directly over the local network | Phone and server on the same network: office, home | Goes nowhere |
| Through the relay | A lawyer in court, on the road, outside the office | An encrypted stream that we do not decrypt |
| Your own domain or a VPN | A firm with a system administrator | Full control |
| Local only | A closed environment without internet | Only inside the perimeter |
It tries the local address and the relay at the same time and uses whichever answers first. The interface shows how it is currently connected: "locally" or "through the relay".
Verification through DNS, and the key never leaves the firm's machine. In the office the same name maps to an internal address — the connection runs directly, but with a real certificate and no browser warnings.
The installer shows a QR code and spells out the code. The lawyer scans it in the app — the address, the server name and a one-time key arrive together. Nothing needs to be entered manually.
What we deliberately do not do
We do not rely on automatic port forwarding: it is disabled on most routers and useless when the provider shares one address. We do not ask you to forward ports by hand — that is the main source of support requests for every product of this kind. We do not force you to install a third-party VPN on every phone.
Operations
A command on Ubuntu or a button in the Mac window. An update never touches case files: data and code are kept separate.
A nightly copy of the database and files, retained for N days, with verifiable restoration.
Service status in the admin area; with support, our alerts and a contractual response.
Moving between environments and exporting files on request. You are not locked in with us.
How deployment proceeds
We establish the volume, the confidentiality requirements and who on the team will work in the system.
Our server or the firm's server. We fix the number of seats and the storage volume; if local models are needed, we estimate the scope of the project.
We install the system, load the files and check the recognition and the quality of the answers on your volumes.
Sessions by role: lawyers, assistants, the administrator of your own server.
The team works in the system on live cases. At the end there is a report: what was found, where time was saved, what to do next.
We will work it out during the case review: our server is almost always enough for the workload, and your own server is needed where there is a written confidentiality requirement.