Platform
Where Sage runs, and who decides what it does
Your organisation picks the environment and the models, and sets what an agent may do on its own. The same product runs in all of them.
Three things hold in every deployment
The product is built on them, so they are not settings to switch on.
It runs in your environment
The models and the work can run on infrastructure your organisation controls. Each screen says what it reads and what it cannot do.
Every answer carries its source
Sage answers from your own records and the sources you approve, and marks each claim back to the document or decision behind it.
A person approves what matters
High-impact actions wait for a named person. Your organisation sets where that line sits, and the platform records the activity.
Where Sage can be deployed
Six environments, one product. Your organisation picks the one its policy allows.
On your premises
On servers in your own building, owned and operated by your organisation.
Your own data centre
A dedicated environment your organisation keeps custody of.
A dedicated private server
Private capacity, supplied through an infrastructure partner.
Private cloud
A dedicated, policy-controlled environment of your own.
Ravon-managed
We run the environment without holding or reading your content.
Fully offline
Chat, knowledge and document work with no internet connection. Connected sources need connectivity.
Hybrid is the usual shape: local models for the work that stays inside, and outbound access only where your organisation switches it on.
Three ways to run it, and who operates what
The product is the same in each. What changes is who owns the hardware and who keeps it running.
- On your premises
- Your organisation
- Private cloud
- Your organisation, in a dedicated environment
- Ravon-managed
- Ravon or an infrastructure partner
- On your premises
- Your organisation only
- Private cloud
- Your organisation only
- Ravon-managed
- Your organisation only
- On your premises
- Yes
- Private cloud
- No
- Ravon-managed
- No
- On your premises
- Your team, with Ravon's guidance
- Private cloud
- Your team, with Ravon's guidance
- Ravon-managed
- Ravon
- On your premises
- Ravon
- Private cloud
- Ravon
- Ravon-managed
- Ravon
What stays inside, and what can leave
Your organisation decides what may leave its environment. The work Sage does locally needs no connection at all.
Stays in your environment
- Questions and documents handled by local models
- Search across your own documents
- The knowledge base and templates
- Drafting, editing, tracked changes and version history
Leaves only if you allow it
- Deep internet research
- Current legislation lookups
- External AI models, behind masking and policy filters
- Connections to outside systems
Ravon does not hold your content and, under the standard setup, cannot read it. Where your organisation enables an external model, requests pass through masking and policy filters first.
What Sage can read
Sage is configured by source type rather than by vendor, so a deployment is described by what it reads, not by a logo wall.
Your documents
Contracts, reports, templates and past work, with their versions.
Records systems
The systems your teams already run, read through connectors Ravon maintains.
Mailboxes
Connected inboxes, where your organisation enables them.
The knowledge base
What the organisation has decided to keep, with the source under each entry.
Public legal sources
More than 13 million Turkish decisions from official free and public sources, counted as of September 2026.
The open internet
Only where outbound access is switched on for that tool.
A missing source does not break a run. Sage works with less context and says so.
What an IT review asks first
The answers your security and infrastructure teams need before a demo.
What hardware does it need?
People use Sage in the browser, with nothing extra on their computers. The server is sized from your users, the models you choose, agent activity and the response times you want. For a typical organisation that can be one server. We have a hardware partner in Turkey and take no commission on hardware.
Which models does it use?
Your choice: local open-weight models, external models for tasks you authorise, specialist extraction models, or a combination. Models running on your own hardware carry no usage fees. Third-party models, hosting and metered services are priced separately and shown up front.
Can it run with no internet connection?
Yes for chat, knowledge and document work. Anything that reaches an outside source, such as deep research or current legislation, needs connectivity by definition.
Who can see what?
Access is set by role, so each user reaches the areas and tools their role allows. The platform records relevant activity.
What happens when Sage is unsure?
It says so rather than guessing, and notes the gap. Work that needs a decision waits for the person your rules name.
A two-day demo, built around your needs
We agree your priorities together and, over two days, show how Sage works on an example workflow we choose with you.
