Products
Software we design, build, sign and support ourselves, on every platform its users work on. Free where it can be, paid where it costs us to run.
See the portfolioBURSUsofts · independent software studio
Our products are used to reach, manage and protect servers and desktops, and they hold the keys to everything else, so we build them that way. The first is BURSU Connection Manager. We also help organisations roll it out across their teams.
Three lines of work, all pointed the same way: software that people trust with access to their machines.
Software we design, build, sign and support ourselves, on every platform its users work on. Free where it can be, paid where it costs us to run.
See the portfolioRolling our products out across a team: installation at scale, shared access with rights per folder, a private instance when a team needs one.
SolutionsZero-knowledge encryption, our own engines for the parts that matter, signed releases on every platform, and rules that fail the build instead of being remembered.
How we workEverything we ship carries the studio's name and the same promises. BURSU Connection Manager is the first.
A connection manager for administrators and engineers: SSH, RDP, WinRM, Apple screen sharing, VNC and file transfer in one window, with every credential in an encrypted vault and an optional shared catalog for teams.
Zero-knowledge sync for people and teams. We store the catalog and cannot read it.
Our own remote-desktop engines: RDP for Windows, AppleRD for a Mac's screen.
When a whole team moves onto our software, the questions change. These are the answers we already have, and the ones we build with you.
winget on Windows, signed apt, dnf and pacman repositories on Linux, notarised images for macOS, and the stores on phones.
Users and groups, folders shared per person, and separate rights to view, to edit, or to reveal a password.
Google and Microsoft accounts, alongside email and a master password that never leaves the device.
Support and security reports go to the people who wrote the code, and a fix ships on every platform together.
A sync service for one organisation, separate from everyone else's, when policy asks for it.
Connecting the shared catalog to the inventory or directory you already run.
The rules behind every product, not a list of features. Each has something checkable behind it.
Master passwords are used on the device and never sent. What we store is sealed with AES-256 and opened only where you are.
The engines that carry a session are our own work, so a fault on a customer's machine is something we fix in days, not report upstream.
Authenticode on Windows, notarised by Apple, repositories signed by us, and a checksum beside every file.
Our products speak English, Russian, Ukrainian and Georgian, and a string that exists in one of them does not ship.
Sales for organisations, support for anything that breaks. Both are read by the people who would do the work.
Which address for what