BusinessOS
For IT and security
Topics to resolve before granting data access. Configuration, permissions and operating commitments are agreed for each project; this is not a list of unconditional guarantees.
On-premise: BusinessOS on your servers
BusinessOS is deployed in your company’s infrastructure. The system, integration module and connections to internal data run within your environment.
For IT and security
Fully local processing
The system and selected model run in the customer’s infrastructure. Verify operation without external calls, resources and updates for the agreed configuration.
External model API
Agreed fragments are sent to the selected model provider. Define data scope, sensitive-information handling, processing location and retention. De-identification does not mean nothing leaves the perimeter.
A pilot environment
Available only after agreeing hosting, data scope, team access and how outputs are delivered or deleted when the pilot ends.
Working with us
Connections and compatibility
For 1C, email, file stores and databases, specify versions, fields and allowed operations. Test each connection separately; an integration category does not imply every configuration is supported.
People and team access
Define roles, workspaces and access across group companies. Agree engineer permissions and how access is granted and revoked.
Models and data use
Training, request retention and processing terms depend on the provider and usage mode. Check them before connecting.
Stopping and recovery
Agree who can stop work, how outputs are preserved and how operation resumes. Recovery and backup timing are specified separately.
Repeated actions
For external messages and writes, test protection against repeated execution after failure. Restrictions and checks apply to the configured scenario.
Updates and changes
An engineer assesses and tests the change with an agreed example, then implements it after approval. Agree rollback before updating.
Support
Specify the channel, response time, included work and engineer cover. 24/7 availability is not assumed.
Ending the engagement
Distinguish data ownership, software usage rights and source-code transfer. Agree export, disconnection and continued operation in the contract.
Agreeing the pilot
Start with your task
In 20 minutes, discuss inputs, the required output and where a person is needed. Then agree what to test and which materials are necessary.