Bring your priorities, existing tools and the first operation you would like to put into practice. The configuration you build here can accompany the conversation.
Starting point: goals, routines and existing systems.Installation
How LogicaOS enters your company
The system runs on a server of yours. This page shows what has to be ready beforehand, what happens on installation day, how the product updates itself afterwards and what stays yours.
ROVEMARK / LOGICAOSInstallation
From your context to the first operation
A guided start. An environment shaped by you.
Implementation starts with what you want to achieve. Goals, infrastructure, access and scope are aligned with the team before configuration.
LOGICAOS01—05
Build my LogicaOSThe conversation defines the environment, license, applications, integrations and responsibilities. Infrastructure, model and external service costs belong in that discussion.
In the proposal: scope, commercial terms and responsibilities.The license is issued to the company. The team assists with environment preparation and installation; connections and permissions follow the agreed scope.
During onboarding: installation access and assisted configuration.Start with a focused goal. Define what agents may access, follow the work in Deck and assess the result before expanding the operation.
Your criterion: a result you can open and evaluate.Add applications, connections and routines as needed. Agree on channels, support coverage and ongoing assistance when contracting.
Going forward: support and expansion under your agreement.What needs to be clear before you begin.
License
Terms, pricing and coverage are defined in your contract. Read the terms and align the scope with the team.
Read the termsModels and services
The environment can use AI providers, infrastructure and external services. Confirm which accounts, usage and costs belong to your setup.
Understand RouterData and access
Define where your environment will run, who can access it and which connections each project can use. Permissions and credentials are part of configuration.
Security and controlSupport and evolution
Support channels, coverage, timelines and assistance need to be in your agreement. The implementation page also explains the update process.
Explore updatesInstallation is assisted
There is no self-service and no public download. The company talks to the team, the license is issued in its name, and the installation address arrives during onboarding, along with the person who stays until the system is running.
Prerequisites
What you need to have
The list is short on purpose. The installer handles almost everything; here is what it cannot decide for you.
A server of your own
macOS, Linux (Ubuntu, Debian, Fedora, Arch, Alpine or SUSE) or Windows 10 build 17063 and above. One machine per company: the server itself is the isolation between companies.
The license key
Issued per company. The installer validates the key before writing anything to disk and stops if it is not accepted.
Node and Python
The installer puts Node at the exact version the package requires. Python 3.10 or higher has to exist on the machine: without it, memory (Logica Mind) is not installed.
No database to contract
Postgres is provisioned on the server itself, with the vector extension (pgvector) memory relies on. No cloud database, no external service to subscribe to.
A private network
The appliance is reached over the Tailscale private network. No port has to be opened to the internet: dashboard, internal Git and SSH sit behind it.
A decision about the disk
With FileVault on, a power cut stops the machine at the password screen and nothing comes up until someone types it. Encrypted disk or unattended restart: the company chooses, and the installation says which one is in force.
Installation day
What happens during installation
One accompanied session, from empty server to a system that answers. Every step fails loudly: nothing is declared ready without being checked.
Installation day01 / 07
License checked
The key is validated before any installation. With no answer from the license server, the installation stops instead of running half way.
Updates
How the system updates itself
An update replaces the whole product, not a piece of it, and distrusts itself at every step.
Signed package
The updater only adopts a file whose Ed25519 signature matches the public key shipped with the product. Without a valid signature it keeps the already verified local copy and warns, which protects against a compromised origin.
Snapshot before touching anything
The system takes a snapshot of the installed code before the first file is replaced. That snapshot is what backs the return.
Migrations checked
Pending migrations are applied to the appliance database and the numbers have to add up. If the check diverges, the update does not continue.
It fails, it goes back
Any error along the way restores the previous version, including the list of services that was running before the attempt.
Your setup stays
Keys, identities and company data are not overwritten by the package: they are preserved and come back along if the update has to be undone.
Sovereignty in practice
What stays with you
Sovereignty here follows from where things live, not from a promise on a sales page.
The data
Conversations, documents and memory live in your server database. We hold no copy, and the end of the contract does not change where they are.
The keys
Secrets live in the appliance encrypted vault. The environment file holds only what is not sensitive.
The way in
Whoever is on your private network is who reaches the system. The appliance has no public address.
Who comes in and who goes out
Each person has their own identity on the appliance, with their role and their projects. Suspending someone takes effect immediately, with no service restart.
The license
It is issued in the company name and it is what authorizes installing and updating.
Shall we look at this on your server?
The conversation starts with the team understanding your machine, your channels and what you want to automate first. The installation date comes out of that conversation, with the name of the person who will follow it through.