Your software.
Your rules.

01Desktop software

A program for the task —
on your computer.

We build a desktop program for work computers: a clear window in the languages you need, one installer, updates at the click of a button. It runs locally, so your data doesn’t go to someone else’s cloud.

What we take on

• We build a program for your task — record-keeping, calculations, file processing, working with equipment: the window, its sections and an action log.
• We package one installer with everything inside, so nothing has to be downloaded later.
• We make the interface in the languages you need, in your brand style.
• We split permissions: anyone can view, but only an administrator can change the system.
• We add one-click updates with signature checks.
• We connect the program to your server, accounting and equipment.

Example — AXM Privacy: one installer with a built-in runtime, a two-language interface and one-click updates from a signed manifest.

Program window · Russian and English

We agree the operating systems and versions to build for before work starts. A publisher signature is arranged separately — without it, the system shows a warning on first launch.

02Work PC privacy

What does your computer
send out?

We show which services, tasks and programs send data out, and switch off what isn’t needed so that any change can be undone. The tool is our own AXM Privacy, which you can download and check for yourself.

What we take on

• We check work computers: system and app telemetry, scheduled tasks, outgoing connections.
• We switch off what isn’t needed, reversibly: the original value of every setting is kept in a log.
• We find programs installed outside the usual list and move them to quarantine.
• We show which programs hold autostart, the camera, the microphone and the network.
• We set up a watchdog: if a system update turns something back on, you’ll see it.

Example — AXM Privacy: a catalogue of 50+ telemetry sources, an app monitor, quarantine and a change log — locally, with no usage statistics.

Found: what this computer sends out

Windows 10 / 11 x64 · 124 MiB · released 24.09.2026

This isn’t an antivirus or a security audit. Changes need administrator rights. The website doesn’t scan your computer — the diagram shows example records.

03App isolation

An untrusted program
gets its own boundary.

Need a program you’d rather not trust with everything? We run it in a separate environment, in a container or with the network closed — a boundary that fits the task, not “all or nothing”.

What we take on

• We run the program in a sandbox — a separate system that writes nothing to your computer.
• We confine the program to a container: no camera, microphone, location or other folders.
• We close the network and camera to the program with the firewall, without removing it.
• We pick the level for each program: what access it needs to work and what it doesn’t.

Example — AXM Privacy: three isolation levels to choose from — a sandbox, an app container and a permanent block.

Sandbox: the program in a separate system

The sandbox needs a suitable system edition and virtualisation. Some programs, browsers for example, won’t run in a container. The firewall doesn’t isolate files.

04Updates and rollback

Updates without surprises —
and a way back.

We make the program update safely: the user clicks a button, the program checks the signature and checksum and downloads only the changes. Changes to the system are logged and can be undone.

What we take on

• We build one-click updates: a signed manifest, and the file is verified against its checksum.
• We serve updates from your server, without third-party stores.
• We ship updates as changes: hundreds of kilobytes instead of the full installer, with the full download as a fallback.
• We build in a log: what changed and what the value was before, with one-click undo.
• We add a release check: the version number must match in every part, or the release doesn’t go out.

Example — AXM Privacy: installed copies catch up with a new version by downloading hundreds of kilobytes, not the whole installer.

The update passed the signature check

No silent updates without the user’s consent: an update starts when they click.

05Mobile and wearable devices

An app in your pocket —
a button on your watch.

We build apps for phones, tablets, watches and other wearables — for the warehouse, the field, service work or your customers: a task screen, photos, sending to your server or work chat. A frequent action goes onto the watch, and equipment connects over Bluetooth.

What we take on

• We build a mobile app for your process: tasks, photos, scanning, sending to a chat or server.
• We put a frequent action on a watch or another wearable — one tap, no phone in hand.
• We connect the app to a device over Bluetooth: scheduled commands, with the link kept alive in the background.
• We build and sign releases and serve them from your own server.
• We build apps for staff, customers and field teams: requests, rounds, inspections, time tracking.
• We make a prototype to test the idea with people before big development.

Example: a device app build with a watch tile and scheduled commands; a service app prototype on a phone.

An app for the warehouse, the field or service work

How the app is distributed — through app stores or from your own server — we decide together for the task.

06Your own server

Your services —
on your server.

We set up a server for your services: services in containers, a database, a domain and HTTPS. Only what’s needed is open to the outside, and your data stays with you, not in someone else’s cloud.

What we take on

• We set up a server for your services: services in separate containers, a database, schedules.
• We connect a domain and HTTPS: the certificate renews itself, and only what’s needed is open to the outside.
• We put bots, email processing and dashboards alongside — all on your one server.
• We set up a workflow orchestrator: schedules, webhooks, email triggers, versions with rollback.
• We document the server: what runs where, who is responsible for what, how to check and restart it.

Example: wholesale processes, dashboards, bots and email processing on one server; only the necessary entry points are open to the outside.

Services run on your server

One server, no clusters and no 24/7 on-call shift. We don’t do penetration tests or cybersecurity audits.

07Backups and watchdogs

Backups are tested.
A failure isn’t a disaster.

We set up nightly database backups, check that they can be restored, and keep a copy off the server. Watchdogs restart a failed service on their own and post to the work chat.

What we take on

• We set up a nightly snapshot of all databases and check that it restores.
• We keep a copy off the server; encryption keys and settings are stored separately.
• We set up watchdogs: a failed service restarts on its own, and you hear about it in your messenger.
• We set up monitoring: data freshness and key and certificate expiry, in chat and in the dashboard.
• We write down how to recover — and test it before it’s needed.

Example: databases are backed up every night with a restore check, a copy leaves the server, and a status summary arrives in the service chat.

Nightly backup taken and tested

A backup saves data, not time: while the server is being restored, services are unavailable.

08Keys and access

Keys kept apart.
Access by role.

We put access in order: keys and passwords out of work folders, each role with its own sections, and server changes shipped as a package with a backup and rollback.

What we take on

• We move keys and passwords out of work folders into a separate vault; documents keep only the key’s name.
• We split access by role: the warehouse, accounting and management each see their own sections.
• We ship changes as a package: backup, dry run, rollout, rollback with one command.
• We set reminders for key and token expiry — before something stops working.
• We find who changed a record and when — from the log, not from memory.

Example: keys live outside work folders, each project has its own sections in the dashboard, and server changes go out as a package with a backup and rollback.

Keys and passwords moved out of work folders

This is putting access in order, not a cybersecurity audit or a penetration test.

09AI on your own hardware

AI without the cloud —
documents stay inside.

We install a language model on your computer with a graphics card. It reads scans and emails, sorts them by type and writes a short summary — nothing goes to someone else’s servers.

What we take on

• We install a language model on a computer with a graphics card — on your network, with no external cloud.
• We extract fields from scans and emails: number, date, amount, counterparty.
• We sort emails and documents by type: request, invoice, other; unclear cases go to a person.
• We write short summaries of long email threads.
• We connect the model to your services through your own server, with key-based access.

Example: a local model on a workstation handles small text jobs — extract, sort, summarise briefly.

Fields from a scan · the document didn’t leave

A local model is weaker than large cloud ones: we take small tasks, and a person checks the result. It needs a computer with a graphics card.

10The whole task

One task —
the whole route inside the perimeter.

A task is usually made of several parts. Pick what you need, and the route through the perimeter lights up: what we connect and where the result ends up.

The routes are examples. We’ll go through your task at the first meeting.

11Getting started

Where to start?
With one task.

A program for your staff, an app for the field, your own server instead of someone else’s cloud, or order on work computers — pick one task, and we’ll agree on a timeline and a verifiable result.

1. The task and where it will run: a computer, a phone or a server
2. A first working version on your data
3. Installer, updates, backups — and ongoing support

Useful to have: a person who knows the process, and access to the computer or server where the program will run.

We agree on access, confidentiality and the scope of work in advance.