Solon

Governed agency inside the operation. Coordinate specialised agents, approved models and controlled tools around accountable outcomes.

Company-specific models · deployment choice

Your expertise. In models you can host.

Why local matters: keep authorised workloads within your chosen infrastructure, encode your terminology and working methods, and decide when models change. Tested open-weight models can reduce dependence on a single provider. Quality, latency and total cost are measured before choosing the deployment.

A deployment can include locally hosted open-weight models such as Qwen, adapted to your terminology and recurring tasks. We can fine-tune model weights or specialist adapters using approved, reviewed examples from your organisation.

Connected sources supply current facts. Training adapts task behaviour. We compare prompting, retrieval and fine-tuning on held-out work before choosing the model, hardware and deployment. On-premises, private European hosting and approved frontier services are options to assess together.

Discuss your deployment requirements

This is our custom-delivery proposition. Scope, permissions, model licences and performance are established per engagement. The public demonstrations do not run an employee agent network or a company-trained model.

03 / AI operations platform

AI with context.
Action with control.

We build agents that work from your operational model. Coordinate investigation, scenario tools and action proposals, with shared evidence, explicit responsibilities and authority checked at execution.

  1. Establish the scope

    Identity, purpose and permissions determine accessible context.

  2. Ground the analysis

    Objects, relationships, evidence and approved tools.

  3. Inspect the proposal

    Separate sourced facts, calculations and generated interpretation.

  4. Authorise the action

    Review, recheck authority, execute and record.

Illustrative workflow · sample dataNext / Icarus
Solon / Security by design

Context is what AI understands.
Authority is what it may do.

An ontology gives AI a model of your business. It does not, by itself, enforce security. We design the controls around the data, models, tools and actions.

01 / DATA ACCESS

Scope what it can see.

Check identity, task purpose and permissions before retrieving context. Exclude or mask fields the workflow should not receive.

02 / MODEL BOUNDARIES

Decide where it thinks.

Choose the model and processing environment. Agree hosting location, provider access and retention for each deployment.

03 / TOOL AUTHORITY

Limit what it can do.

Give each workflow specific tools. Validate their inputs and check action permissions in the application, separately from the model's instructions.

04 / REVIEW & EVIDENCE

Keep people accountable.

Test representative and adversarial cases. Inspect proposed changes, route consequential actions for approval and record outcomes. Protect the access and retention of the evidence itself.

Solon / Private AI

Keep control of what leaves.

We design a private gateway around your document workflows. Original files and identity lookups stay in the agreed private environment. Your rules determine which model may receive which information.

Extraction, search, calculation and AI processing stay within the institution’s approved environment, including its authorised sovereign models. No document content is sent to an external AI provider.

01 / Private source

Read and compare locally.

Supplier A: contract DOC_01 authorises €5,000; invoice DOC_02 requests €5,400. Local calculation identifies a €400 difference.

02 / Internal model context

Use the approved private model.

Supplier A / DOC_02 exceeds DOC_01 by €400. No approved amendment was found in the supplied records. Prepare a request for supporting evidence.

Context remains subject to the employee’s access rights.
03 / Employee review

Restore context under permission.

The private workspace assembles the draft with the authorised recipient, €400 difference and source links. An employee checks the evidence before any action.

Masking names does not guarantee confidentiality. We test indirect identification, business secrets, hidden content, logs and attempts to bypass the rules. Access and retention also apply to the disclosure record.

Illustration with synthetic records. No files are uploaded and no AI model is called. The gateway is a proposed capability to develop and validate for each engagement.

Begin with the question

What could your data make possible?

Start with a scenario and the systems involved. An initial conversation does not require confidential data.

Request a demonstration