Technical overview
How your company's information becomes a brain.
Kortia reads what your company already produces, in meetings, documents and systems, and organises it all in one place. This page shows the path of each piece of information: where it comes in, what the AI does, where a person approves and where it is stored.
Everything becomes a note with a source
Every decision, deadline or task points to the document or the minute of the meeting it came from.
The AI suggests, a person decides
Anything that meaningfully changes the brain is approved before it is written.
One instance per company
Your data lives in its own environment, separate from every other client's.
Overview
Three inputs, one brain, four uses
Inputs
Processing
Brain
Use
Connections
calendar, folders, email, finance
Scheduled read
read only, rule-based maths
↓ files from folders
Documents
contracts, proposals, spreadsheets
Queue and identification
AI: type, owner, deadlines, clauses
Meetings
online, in person, live
Transcript and package
AI: decisions, tasks, questions
Company brain
notes with source and date
- Clients and projects
- Contracts and records
- Meetings and decisions
- Contacts
- Finance
- Change log
One instance per company
Chat
question and answer
Agents
work by area
Dashboards
figures and reports
Alerts
what needs attention
The path depends on the input. System data is read on a schedule and goes straight in, with no AI in the maths. Documents and meetings go through the AI and wait for a person's approval. Files from connected folders follow the same path as an uploaded document.
Input 1
Connections to your systems
Each connection reads only what was authorised, in the folders and accounts you choose. Access is read only: Kortia does not change, delete or send anything in your systems. The only action outside Kortia is turning on Google Meet's automatic transcription before a meeting.
| Connection | What it reads | When | Where it goes |
|---|---|---|---|
| Google and Outlook calendar | Events from one day back to one day ahead | Every 5 minutes | Meeting record, which starts the meeting flow |
| Google Meet | Meeting transcript and participants | After the meeting ends | Meeting flow |
| Google Drive, OneDrive and SharePoint | Files in the chosen folders | Every 10 minutes | Document queue |
| Outlook email | Messages fetched at the time of the request | In the chat and when preparing a meeting | Not stored: used as context, then discarded |
| Finance (Asaas) | Balance, charges, subscriptions and statement | Every 2 hours | Financial snapshot, dashboards and alerts |
| Your own system | Whatever is agreed in the project | Agreed times | Local database, alerts and a summary note |
Financial and system data is handled with calculations and rules, not with AI. The AI comes in later, when someone asks in the chat or an agent uses the data.
Inputs 2 and 3
Documents and meetings, step by step
Document
1. Input
upload, chat or folder
2. Queue
copy and record
3. Approval
when the batch calls for it
4. Read
PDF, Word, spreadsheet
5. AI identifies
type, owner, deadlines
6. Write
record, text, original
Meeting
1. Capture
calendar, Chrome or Meet
2. Transcript
who said what
3. AI package
decisions and tasks
4. Check
quote vs transcript
5. Approval
a person reviews
6. Write
summary, project, log
In purple, the point where a person decides. For documents, approval is requested on a folder's first read and for uploads of more than 20 files. For meetings, the package always waits for approval.
What happens to a document
- Formats: PDF, Word, spreadsheet, CSV, text and image, up to 50 MB. Scanned PDFs are read too.
- The AI extracts: document type, who it belongs to, area, parties, clauses, deadlines, amounts and contacts.
- What is stored: a record with the fields, the full text, the original and the links to other documents, such as proposal and contract or contract and amendment.
- No duplicates: the same file never comes in twice. A new version replaces the old one and keeps the history.
- Reversible: writing is all or nothing, and every import can be undone.
What happens to a meeting
- Capture: the calendar flags that the meeting is starting. Recording only begins after someone confirms the notice to participants.
- The package holds: summary, decisions, tasks with owner and deadline, requirements, questions and contacts.
- With proof: each item carries the sentence that was said and the minute. If the sentence isn't in the transcript, the item is marked as uncertain.
- On approval: the client's project is updated with next steps, requirements and questions. The audio is deleted.
- Over time: Kortia learns arguments, objections and promises made, and keeps each client's stage up to date.
Agents
Who works on top of the brain
Each agent looks after one area and is switched on per company. They all read the same brain, so each one knows what the others recorded.
| Agent | What it uses | What it delivers |
|---|---|---|
| Meetings | Calendar, recording, transcript and participants' recent emails | Meeting package with decisions and tasks, company learning and each client's status kept current |
| Finance | Charges, subscriptions and statement | Cash position, 90-day forecast, overdue items, dashboards, reports and alerts |
| Salespilot | Client note, project and special terms | Proposals in the company's template and upsell opportunities |
| Marketing | Brand kit, with colours, tone of voice and logos | Content ideas and pieces in the brand's style |
| Tailor-made | A system specific to the company | Rules, alerts and reports for that business |
Control
What's automatic and what waits for a person
| Situation | How it comes in | Detail |
|---|---|---|
| A folder's first read | approval | File by file. A rejected file only comes back if it changes. |
| Upload of more than 20 files | approval | Shows the cost estimate before processing. |
| Meeting package | approval | Names and items can be corrected before approving. |
| Notes during a live meeting | approval | Item by item, while the meeting is happening. |
| Important learning | review | Becomes a review task for the team. |
| New finance rule | confirmation | The AI suggests the category; it's only saved with your yes. |
| Recording a meeting | confirmation | Someone confirms the recording notice and starts it. |
| New file in an approved folder | automatic | Goes straight to reading. |
| Calendar, finance and systems | automatic | Read on a schedule. |
| Transcript of a recorded meeting | automatic | Saved when the recording ends. |
Data and security
Where your data lives
Your team
browser, with login
↓ HTTPS, own address →
Your company's instance
Panel and agents
chat, screens, queues
Brain
notes in Markdown
Local database
queues and state
Originals
files received
text for analysis
AI model
Anthropic Claude
read only
Your systems
Google, Microsoft, finance
encrypted copy
Backup
off the server
Another company: another instance, no access to this one
Each company has its own container, storage and network. What leaves the instance is the text sent to the AI model for analysis and the encrypted backup copy. From your systems, the instance only reads.
Isolation and access
- One instance per company, with its own address and login per user.
- Connections with read-only permission, in the accounts and folders you authorise.
- Disconnecting a source deletes the credential. What was already read stays in the brain.
Sensitive data
- Email is not copied or stored: it is read at the time of the request.
- Brazilian ID numbers (CPF and RG) are masked in saved notes. The original is kept apart, out of search.
- Meeting audio is deleted after approval. With cloud transcription, the provider deletes the transcript when it's done.
Trail and undo
- Every change gets a line in the client's log and in the general log.
- Writes are all or nothing: an error halfway never leaves half-written data.
- Imports can be undone, including what they changed in other notes.
The data is yours
- The brain is made of Markdown files, an open format readable without Kortia.
- AI cost is measured per step and billed in credits, with an estimate before large batches.
In development
What's next
These items are not in the product yet. They are on the roadmap and come in by client priority.
Per-connection permissions
choose who on the team sees each source's data.
More connections
WhatsApp, CRM and ERP, on top of the ones that work today.
Contract deadlines agent
a heads-up before expiry, renewal and price adjustment, from the records that already hold those dates.
Email beyond lookup
following threads and incoming invoices.
Want to see this architecture with your company's data?
We walk a real document and a real meeting through it, from start to finish.