Our approach
Your knowledge. Your choice of deployment.
Why we offer Skientia Cloud and Skientia Private, and how we build a lasting working relationship around each.
Choose control and responsibility together
Organizational knowledge is useful when people can find it, understand why a decision was made and trace an answer to its sources. Teams differ in where that system should run and who should operate it. We offer two commercial packages around the same platform, so deployment fits the organization.
Cloud: done for you
Skientia Cloud combines a hosted subscription with scoped onboarding. We help connect the agreed sources, configure access and establish a useful workflow. We operate the service and manage software updates. Your team controls source permissions, user access and what belongs in the knowledge base. Training and additional services are defined in the proposal.
Private: done with you
Skientia Private combines an annual software license with a separate implementation project. We work with your IT team on installation, integrations, training and acceptance on your approved infrastructure. Your team owns day-to-day operations unless managed operations are contracted separately. You pay infrastructure and model-provider costs. Every Private project starts with an assessment and a paid pilot.
A continuing product, with controlled updates
An annual Private agreement covers the licensed scope, eligible updates and defined support. Your administrators approve installation. The agreement specifies deployment allowances, user bands, renewal and expiry behavior. Connected checks or offline renewal are selected during assessment and must be qualified before rollout. A licensing outage should not put existing knowledge at risk. This offer is not a perpetual license.
Be explicit about data and access
Running the application on your servers does not by itself keep every processing step inside your network. AI providers, source systems and support access have their own boundaries. We document them before deployment. Commercial reporting is limited to information needed for licensing; content access and operational diagnostics require separately agreed permissions. Fully disconnected operation must be assessed and tested against your actual requirements.
Start with evidence, then expand
We begin with a named workflow, a limited source set and measurable acceptance criteria. The pilot checks usefulness, access behavior and whether the deployment can be operated and recovered. The proposal makes pricing, responsibilities and support clear. We expand from that evidence, keeping improvements in the shared product rather than creating an isolated fork for each customer.