Route access through Cirql
Our gateway sits between company context and connected agents. It provides the path for supported tools to request context under the access configured for the engagement.
In place · Context GatewayThe Cirql platform
Own your context.
Control what comes next.
AI can keep getting better. Your company’s knowledge should keep belonging to you.
Cirql’s gateway is in place today, connecting approved agents to your company context and generating receipts for activity routed through it. Data integrity and the integrity of our platform are central to how we build, operate, and improve the system.
One company foundation.
A controlled path to AI.
Keep your records, business relationships, and know-how together. Give compatible agents a way to request useful context for the work you authorize.
Your company
ERP, CRM, email,
documents, team knowledge
Cirql
Company context
Connected records, searchable meaning, business relationships.
In place today · Cirql Gateway
Gateway + receipts
A controlled path to company context, with receipts generated for gateway activity.
Request context
Receive approved evidence
Receive approved evidence
Your approved AI
Search, reason,
draft, automate
Ownership and processing are different.
You retain ownership of your source data. A hosted AI provider still processes the context sent to it, and Cirql’s infrastructure processes data to deliver the service. Approved destinations, retention, training restrictions, and access terms need to be agreed for your deployment. A gateway alone does not prove that a provider retains nothing.
Integrity is a core priority
Useful AI.
Accountable infrastructure.
The gateway and receipts are part of the platform today. We continue to build on that foundation because your company’s information, the way it is accessed, and the reliability of our system deserve ongoing attention.
Keep a record of the activity
The gateway generates receipts for activity routed through it, giving your team a record to review when understanding how the system was used.
Available today · Gateway receiptsKnow your agents
A centralized view of agent ownership, purpose, model selection, and permissions across supported tools.
Planned expansion · Agent RegistryExtend review and verification
Broader human approval workflows and checks against source evidence, alongside expanded audit history and cost visibility.
Planned expansion · Approvals & verificationA receipt for the work.
A record you can inspect.
Our gateway generates receipts today. They give your team a record of gateway activity to review, support investigation, and make system use more accountable. The fields captured depend on the connected workflow.
Example scenario · illustrative content- Business task
- Prepare a service follow-up
- Context needed
- Equipment and service history
- Access path
- Connected agent → Cirql gateway
- Record
- Gateway activity generates a receipt
- Review
- Inspect the information captured for that workflow
Your trust is an ongoing responsibility.
We treat customer data integrity and platform integrity as core operating priorities. That means being clear about ownership and access, keeping activity reviewable, and using what we learn to improve the system. Receipts support accountability; they do not replace sound permissions, careful configuration, or human review.
The gateway and receipts are current capabilities. Agent Registry, broader approvals, verification, and expanded audit and cost views remain planned enhancements. We confirm the connected workflows and scope with you.
Models should be replaceable.
Company memory should not be.
Build a company asset that lasts beyond a conversation or a model subscription. New tools should start with the knowledge you have already connected.
Your data stays yours.
Hosting and processing do not transfer ownership of your source records. The service agreement defines access to derived context, export formats, retention, and handover.
Your model choices can evolve.
Keep the context foundation separate from the model. Moving to another supported agent or provider may need integration work, but should not mean recreating your company knowledge.
Your agency works within your permissions.
Partners can build on a client’s approved context. Account control, billing, access, and handover are agreed upfront; one client’s data is not another client’s context.
Useful AI.
Clear responsibilities.
Visible costs.
The managed layer has a cost because it keeps your company knowledge organized, available, and ready for the next tool.
Pay for the parts you use.
Start with a free intake and data plan. Storage and embedding are usage-based. Ingestion, model usage, retrieval, custom builds, and support may add costs under your agreed scope.
Additional control has its own scope.
Advanced governance and private deployment may carry additional platform, processing, or infrastructure fees when available. We agree on capabilities and pricing before activation.
Explore ways to work with CirqlThe starting point
Start with managed context.
We handle the context infrastructure and help connect your approved tools. You can explore the platform without installing local hardware.
Get started for freeComing later · Cirql SovereignMore control over
More control over
where it runs.
Private and local deployment are on the roadmap for companies that need greater control over infrastructure and model processing.
These options are not available to select today. Deployment requirements, supported models, pricing, and timing will be announced as they are ready.