opengate

Products

Three products.One index.

Ask your records. Get the source.

People ask in their own words, and every line of the answer shows the document it came from.

About Assistant

One question, three systems, one answer.

The contract from Drive, the invoice from 1C, the payment from the bank, each line with its source.

«Шарт қашан аяқталады?»AK
«Когда истекает договор?»DA
shart = dogovor = contractone term
Contract No. 77-A runs until 31 Dec 2026.clause 9.1

Russian and Kazakh in one question

Mixed languages, one term spelled the Kazakh way and the Russian way, one counterparty named three ways in four systems. All resolve to the same records.

“that act for sixteen million”DA
matched by meaning and by wording3 records
Act No. 1216 400 000 ₸, 17 Febmatch
E-invoice, bank statementthe two beside it2 more
Act No. 12 of 17 Feb for 16 400 000 ₸, closed by the e-invoice and the statement.3 sources

A rough question finds the exact record

Half a name, a rough date, a figure someone remembers. The question is matched by meaning as well as wording, so it finds the record and the two beside it.

Routine work, done before you arrive.

Each agent runs one recurring task on a schedule, with its owner's rights, and writes nothing without a person.

About Agents

One run, on the record

What it read, what it prepared and who approved it, beside the definition of what it may touch.

Acts vs e-invoicesa name a colleague recognisesagent
owner: dana@financeDA
every Monday, 06:00schedule
last run: 41 read, 3 writtentoday, 06:41ok

Named, scheduled, attributable

Each agent has a name a colleague would recognise, a schedule, and an owner whose identity it runs under. The log names the owner, and the failure card reaches them.

triggerschedule or event
read1C sales, Drive/Finance
writeone sheet, one tab
approvalowner, before any write
ownermissing, so the agent does not exist yet

Defined before it runs

A trigger, a read scope, a write scope, an approval rule and an owner. If any of the five is missing, the agent does not exist yet.

Everything you run, on one index.

The systems you already run, joined into one index with the permissions each of them sets.

About Context

One index over every source

Every document arrives with its system's permissions, so the index answers each person with only what they may open.

1source1C over OData, cursor: DataVersion
2fetchdelta on change, resumable41 changed
3normaliseone record shape, permissions per itemrequired
4indexthe index never knows which system it came from

Written against one contract

Cursor-based sync, delta on change, and a record shape the index reads without knowing which system it came from.

Drive: per-file sharingread from the source at ingestioncaptured
1C: user roleread from the sourcecaptured
Bitrix24: access rightsread from the sourcecaptured
rules written by hand on our sidethere is no such table

Permissions arrive with the content

Each source's sharing model is read at ingestion and becomes the check that runs on every query. We translate rules; we never assign them.

Every department, inside its permissions.

An answer or an action never reaches past what the person asking may already open.

1query“payroll for August”
2permission filterinside the query, before retrieval11 of 208
3candidatesdrawn from the permitted set only
4answerone path for search, answers and agentsheld by a test
candidates → filter → answer

The check runs inside the query

Retrieval starts from the set the asker may read. Filtering results afterwards would already have read what it then hides.

FDCFO: “payroll for August”Drive/Finance, 1C11 documents
FDanswer, with the figurePayroll_08.xlsxgranted
STIntern: the same questionno permitted document0 documents
STanswer: no access, and no hint of another resultrefused

Two people, one question, two results

Neither is told the other's result exists. The difference is a different retrieval, and a different count.

Connected to what you already run.

All three read the same index, so the next product starts from what the first one connected.

Driveper-file sharing, read from the source208 files
Gmailthreads, one per conversation523 threads
delta on changeTokenevery 10 minutes, resumable

Google Workspace

Drive and Gmail. Per-file sharing read from the source, which is what makes the permission check real.

Salesacts, e-invoices, payments1 240 records
CounterpartiesBIN, IIK, contracts312 records
delta on DataVersionover OData, user role captured

1C

Sales, counterparties and the product catalogue over OData, delta on DataVersion. The records this market searches by.

Deals, contactsover REST, access rights captured58 open
Taskswith their assignees140 open
outbound webhookseach change arrives as it happens

Bitrix24

Deals, contacts and tasks over REST, with outbound webhooks carrying each change.

Runs where your data lives.

Assistant, Agents and Context run on your servers, or in a cloud region in Kazakhstan.

On-premiseyour own servers, your own network
Air-gappeda self-hosted model, no egress
Kazakhstan datacentrethe same package, a named datacentre
Data leaves the perimeternothing is sent out to be searched

Deployed where the data must stay

The same index and the same check, packaged for a datacentre you name. Nothing leaves the perimeter to be searched.

Providerunder your own accountyour key
Retentionnothing kept after the answerzero
Trainingin the terms and at the gatewayexcluded
Modelswappable without touching the indexswappable

Your data trains nobody

The answering model is yours to choose and yours to key. Retention is zero, training is excluded, and both are enforced at the gateway on every call.

Point one of these at your company.

Tell us what you run today. We will say which product fits and what it takes.