Eyeward is a platform where a company — or a person — builds a system around their own process without programmers: modules with fields, records, lists, boards and Gantt charts, rules, relations, documents and charts. Around it sits a complete workspace: mail on your own domain, chat, files with an office editor, websites, semantic search, an assistant running on your own model and access for external AI agents. Eyeward is a platform where a company — or a person — builds a system around their own process without programmers.
Orders
+ rules, statuses, relations
Pumping station NS-40
+ versions, comments, assignments
A module describes one entity in your process: an order, a machine, a client or a household expense. You put its fields together with the mouse, and the platform builds the input form, the record list, the edit history and access rights around them. Schema edits collect in a draft and apply with a single Save; every module version stays in the history, ready to roll back to. A module describes one entity in your process. You put its fields together with the mouse; the platform builds the form, the list, the edit history and access rights.
Unsaved changes
Fields
Form tab “General”
Add a field
That’s plenty for the example — remove a field to add another
| Category | Field types | Qty |
|---|---|---|
| Basic | Text, Textarea, Number, Checkbox, Date, Datetime, Time, Time range, Duration, Email, Phone, Password, Code, Currency, Percent, Color, Rating | 17 |
| Choice | Select, Status | 2 |
| Relation | Relation, Record card, Rollup, Stage rollup, Row status | 5 |
| Advanced | Table, Row dependencies, Progress, Chart, Attach, Attach Image, JSON, Button | 8 |
| System | Heading, Divider. One more system field — Title — exists in every module and isn’t part of the palette | 2 |
A record card has a header, a tabbed form, a sidebar and a comment feed. Only the fields you changed are saved, so two people can edit the same record at once: you can see who’s viewing it, and a field a colleague is editing shows a lock. Only the fields you changed are saved, so two people can edit one record at once, and the history keeps every change.
Record created
Pick a version: roll back a single field or the whole record
Note. Deleting a record is permanent: records have no trash bin. Before deleting, a dialog lists everything that goes with the record, and its file folder moves to the Files trash. An Excel import doesn’t run form rules — computed values appear once the record is saved for the first time.
A task can be issued on a record, on one of its fields, on an email, on a chat conversation or on its own — it doesn’t need a record. Inside are a checklist and stages that hand over to the next assignee. Task automations create tasks for you: when a record is created, a status changes, a date comes up or an email arrives. A task can be issued on a record, an email, a chat or on its own — and task automations create them by themselves when an event happens.
Try it on the mockup: build a rule, fire the event and take the task through its stages.
A task automation rule builder. Pick the event, the condition, the task template and the assignee: the rule is retold in one sentence, with the task it would create next to it. “Fire the event” plays the event on a record or an email, and the task appears on the board below.
Module OrdersField Statusbecomes Ready to ship
What to do Prepare the shipment: {{record.title}}Priority HighDue in 2 daysChecklist 4Stages Kit check → Paperwork → Shipping
Person field ManagerThe value of the person field at the moment the rule fires.
When “Status” becomes “Ready to ship” in “Orders” — and the condition holds: Order amount is over 100,000
A task is created for the person in “Manager” · Not while the previous one is open
Prepare the shipment: Pumping station NS-40
Igor Savchuk
Checklist: 4Stages: 3
Task on the record
Using the record ЗАК-0042
Record ЗАК-0042 is saved: Status was “In production”, now “Ready to ship”.
The board of tasks handed out by Marina Gulevich and an open task card. Click a card on the board to open it. The action buttons move the task between columns, “Stage done” hands it to the next assignee, and the checklist boxes record who ticked each item.
Empty
Empty
In progressOrders · ЗАК-0045
Created by rule “Orders: next step”
Next: “Shipping” — Denis V. You act as the assignee — Olga R.
Note. A rule acts on behalf of the person who created it: without their permission to assign tasks, or without access to the record, no task appears and the reason stays in the log. “Revoke” and “Delete permanently” are different actions; the second erases the history too, so it is a separate role permission.
A view answers one question: how should the records be shown? There are four view types — List, Kanban, Gantt chart and Calendar. Each can be added several times under its own name, and one view can serve several modules. Dragging a card or a bar is an ordinary record edit: it lands in the version history and in notifications. There are four view types — List, Kanban, Gantt chart and Calendar. Dragging a card or a bar is an ordinary record edit that lands in the version history.
Gantt chart of the Production module: twelve stages across orders, grouped by workshop — machining, painting, assembly and welding; a weekly scale from late July to early October 2026, with an amber line for today. The demo shows the product’s gestures: a bar is moved, stretched by its edge, and its progress dragged.
List of orders: title, client as a link, status as a colored badge, delivery date, order amount, discount and an urgency mark — ten rows. Quick filters for Client and Status sit above the list and narrow both this list and the board next to it.
The same orders on a board by status: Draft, Confirmed, In production, Ready to ship, with Shipped past the right edge of the board; each card shows the name, client, amount and delivery date. A card moved to another column changes its status in the list too.
No cards
No cards
No cards
No cards
No cards
A calendar has no events of its own. It shows the records of the view’s modules as layers — meetings, delivery dates, the production stages from the Gantt chart above — each layer with its own color and its own start and end fields. Move an event or pull its bottom edge and the record’s dates change, the same way as on the Gantt chart. A busy resource isn’t locked: the calendar asks again and highlights the overlap. A calendar has no events of its own: it shows module records as layers. Move an event and the record’s dates change.
Calendar of the “Week plan” view in Week mode, September 14–20, 2026: six meetings on the hour grid; the all-day row holds the delivery date of order ЗАК-0042 and three production stages as bars across days; an amber line marks the current time. Three layers sit above the grid, and each can be switched off. An event moves by mouse, by arrow keys or with the buttons in the card; the card on the right shows which record fields changed. The “Move onto a busy slot” button puts a meeting into a room that is taken: the calendar asks for confirmation and outlines both events.
That time is taken.
Drag an event with the mouse, or select it and move it with the arrow keys.Select an event and move it with the buttons in the card below the grid.
Talver-Agro: NS-40 acceptance
Moving or stretching the event changes these record fields.
All layers are off, so the grid is empty. The records themselves are untouched.
With an event focused: ←→ day ↑↓ time Shift↑↓ length
Left and right arrows move the event by a day, up and down by half an hour. Shift with up or down changes its length.
Note. The Gantt chart doesn’t reschedule by dependencies on its own: a task has one predecessor, with no link types or lags. The calendar doesn’t forbid double-booking a resource — it highlights the overlap and asks again. Events reach your phone’s calendar through a subscription link (.ics): edits made on the phone don’t come back into the records.
Automation is put together from if-then conditions, formulas and action buttons — there’s no code to write. Rules change how the form behaves, transitions move the status by themselves, actions create records in another module with one click, and rollup fields total up child records. Automation is put together from if-then conditions, formulas and action buttons — there’s no code to write.
If all conditions (AND) applies
Then
Record ЗАК-0042 change the status and quantities
The Shop field is hidden in the form — the rule didn’t apply
Status transition
When a linked record is created · Production
Status Confirmed In production
| Mechanism | How it works | Limits and numbers |
|---|---|---|
| Rules | “If…” — conditions in AND/OR groups. “Then…” — show, hide, make required or optional, read-only, allow editing, set a value, block saving, show in one column. A target is a field or a whole form section; rule order sets priority, and rules also run row by row inside tables.12 operators, 3 nesting levels, 9 actions | 12 operators, 3 nesting levels, 9 actions |
| Formulas | A string that starts with “=”: references like {field_key} and {table.column}, operators + − * /.17 functions: sum, min, max, round, ceil, floor, abs, date, today, isodate, addmonths, maxdate, mindate, time, timediff, count, countunique. No branching or comparisons | 17 functions: sum, min, max, round, ceil, floor, abs, date, today, isodate, addmonths, maxdate, mindate, time, timediff, count, countunique. No branching or comparisons |
| Statuses and transitions | Colored statuses and a starting status; Requires approval, lock editing after approval, record cancellation. A transition changes the status by itself — when the record is saved or when a linked record is created.2 triggers; conditions on the count and totals of child records | 2 triggers; conditions on the count and totals of child records |
| Record actions | Create records from line items, create one record, create a linked record, create records on a cycle. Created records update when the source is saved.4 types, 5 value sources; on re-run — always create, skip or update | 4 types, 5 value sources; on re-run — always create, skip or update |
| Records on a cycle | Shift rotas like “2 on, 2 off”, maintenance plans, payment schedules: a run dialog with a period, a preview and progress.3 modes: step sequence, days of the week, auto | 3 modes: step sequence, days of the week, auto |
| Rollups | Rollup — sum, count, minimum, maximum or average over child records, with a filter. Stage rollup — over the records of the previous stage.5 aggregations; computed on the server, read-only in the form | 5 aggregations; computed on the server, read-only in the form |
| Resource planner | A table-field mode that computes the plan automatically: the server spreads the work over the free time of machines, crews or meeting rooms.Takes the queue, urgency, working hours and norms into account | Takes the queue, urgency, working hours and norms into account |
Note. The rule, status-transition and record-action editors currently show Russian labels only — the English interface isn’t complete there yet.
A relation defines a parent → child link and is created on the child module’s Relations tab. The form then gets a “linked to” field, and the record card gets a Relations tab with a graph. A relation can be made required or switched off for a while without losing data; cycles between modules aren’t allowed. A relation defines a parent → child link: the form gets a “linked to” field, and the record card gets a Relations tab with a graph.
Note. The relation editor currently shows Russian labels only — the English interface isn’t complete there yet.
A document is a print template in Word (DOCX) or Excel (XLSX) with a data scope: one record, a list of records, or the company. You build it in a visual editor and publish it in versions; people get the finished file from the Document button on a card, or from Documents in a list — then it covers the current selection. A document is a print template in Word (DOCX) or Excel (XLSX). People get the finished file from the Document button on a card or Documents in a list.
Designer
Invoice No. meta.id
Buyer: client.title
Delivery date: format_date(delivery_date, 'dd.MM.yyyy')
| # | Item and quantity | Amount |
|---|---|---|
| Repeat over a collection · items | ||
| index | item.name × item.qty | format_number( |
Total: format_number(amount, 2) Br
Amount in words: amount_words(amount, 'BYN')
Preview · ЗАК-0042
Invoice No. ЗАК-0042
Buyer: Talver-Agro
Delivery date: 18.09.2026
| # | Item and quantity | Amount |
|---|---|---|
| 1 | Pump NSh-40 × 4 | 74 400,00 |
| 2 | Directional valve R-80 × 6 | 40 800,00 |
| 3 | Hose RVD 1SN DN12 × 20 | 13 200,00 |
Total: 128 400,00 Br
Amount in words: Сто двадцать восемь тысяч четыреста рублей 00 копеек
Invoice No. ЗАК-0045
Buyer: Olvata-Energo
Delivery date: 29.08.2026
| # | Item and quantity | Amount |
|---|---|---|
| 1 | Oil station MS-250 × 1 | 186 000,00 |
| 2 | Pressure filter FN-25 × 4 | 14 000,00 |
| 3 | Commissioning × 1 | 14 000,00 |
Total: 214 000,00 Br
Amount in words: Двести четырнадцать тысяч рублей 00 копеек
Invoice No. ЗАК-0049
Buyer: Lemvara-Moloko
Delivery date: 22.07.2026
| # | Item and quantity | Amount |
|---|---|---|
| 1 | Pump NSh-32 × 1 | 8 100,00 |
| 2 | Delivery × 1 | 1 200,00 |
Total: 9 300,00 Br
Amount in words: Девять тысяч триста рублей 00 копеек
The template engine prints numbers and amounts in words the Russian way — this is its real output.
| Group | Functions | Qty |
|---|---|---|
| Aggregates | sum, avg, min, max, count, join, distinct | 7 |
| Collections | filter, sort_by, find, flatten, explode, merge | 6 |
| Computed values | sum_by, with_field | 2 |
| Grouping and calendar | group_rows, split_days | 2 |
| Dates | format_date, date_add, date_diff, min_date, max_date | 5 |
| Numbers and money | format_number, format_currency, format_percent, amount_words, number_words, payment_terms | 6 |
| Strings | upper, lower, trim, concat, substring, length, split | 7 |
| Math and logic | round, floor, ceil, abs, if, coalesce, empty | 7 |
Note. There’s no PDF export: you download a .docx or .xlsx file and print it from Word, Excel or LibreOffice. XLSX templates have no nested loops.
Charts are built in an editor from module data. A finished chart goes into a workspace as a block, or straight into a record form as a Chart field. Every chart has a draft and a published version, so readers never see half-finished edits; results are cached and refreshed in the background. Charts are built in an editor from module data and go into a workspace as a block or into a record form as a Chart field.
Orders by status Count · Order amount, Br
10orders
| Group | Types | Qty |
|---|---|---|
| Comparison | Bar, Horizontal bar, Waterfall, Pareto, Combo, Pictorial bar, Lollipop | 7 |
| Trends | Line, Step line, Area, Bump (ranking), Candlestick, Stream | 6 |
| Proportion & structure | Pie, Donut, Half donut, Nightingale rose, Sunburst, Treemap, Funnel, Pyramid | 8 |
| Distribution | Scatter, Bubble, Effect scatter, Heatmap, Calendar heatmap | 5 |
| Radial & indicators | Activity rings, Radar, Polar bar, Radial bar, Polar line, Gauge | 6 |
| Relations & flows | Sankey, Chord, Network, Tree, Parallel coordinates | 5 |
Production and sales
Production stages by workshopProduction · Count
Global search opens with Ctrl/Cmd + K, or as soon as you start typing, and takes you straight to the field where a record matched. Semantic mode finds records by the meaning of a phrase: embeddings are computed by a separate machine running Ollama on the installation owner’s network, and if it’s unavailable, search quietly stays text-based. Press Ctrl/Cmd + K or just start typing — search takes you to the field where a record matched, and semantic mode searches by meaning.
A mockup of the global search window over the order list: the query “pump”, the Include panel with All modules, Comments, Chats, Mail and Files toggles, Pump NSh-32, emergency replacement and Pumping station NS-40 in the Orders group, then chats, mail and files; the sparkle button adds a record found by meaning; key hints at the bottom. The toggles and the sparkle are clickable and change the results.
Search... pump
Start typing to search
Searches records across every module you can access, plus your chats, comments, mail and files
No results found
Try a different keyword
(18600 × 4 + 6800 × 6) × 0.95
= 109 440
That’s not an expression — no calculator card, the bar simply searches records, mail, chats and files.
Examples
Enter copies the number, just like in the app
Every user has My files, and every company has a space of its own. Most formats open right in the browser: office documents are edited in ONLYOFFICE, together if you like, and text and Markdown in the built-in editor. Record files live in the same structure, in a folder the platform creates for each record. Most formats open right in the browser, and office documents are edited in ONLYOFFICE — together if you like.
| Group | Formats | What you can do |
|---|---|---|
| Images | image/*Zoom from 1 to 8× | Zoom from 1 to 8× |
| Video | video/*Seek without a full download, 0.25–2× speed, subtitles and chapters from neighboring .srt, .vtt, .ass, .ssa files, picture-in-picture | Seek without a full download, 0.25–2× speed, subtitles and chapters from neighboring .srt, .vtt, .ass, .ssa files, picture-in-picture |
| Audio | audio/*The same player: volume boost, a mini player, remembered position | The same player: volume boost, a mini player, remembered position |
| Office | 43 extensions: docx, xlsx, pptx, odt, pdf, djvu…View and edit in ONLYOFFICE, together too; 22 formats edit without conversion | View and edit in ONLYOFFICE, together too; 22 formats edit without conversion |
| Text and code | 45 extensions plus text/*The built-in editor | The built-in editor |
| Markdown | .md, .markdown, .mdxEditor, Split and Preview modes | Editor, Split and Preview modes |
| Archives | .zip, .jarA file tree without unpacking | A file tree without unpacking |
| 3D and CAD | 25 formats: glb, gltf, obj, stl, fbx, 3mf, STEP, IGES, BREP, 3DM, IFC, G-code…View the model in the browser | View the model in the browser |
A working mockup of a text file’s version history: pick a version to see how it differs from the current one; Restore makes the chosen version current, and the present state moves into the history.
Version 2 → Current
This is the file’s content right now. Pick an earlier version to see what changed.
The current state will not be lost: it becomes the next version in the history, and you can come back to it the same way.
The mail client is built into the platform and runs on the installation’s own mail server; your mailbox is created the first time you open Mail. Messages link to records, can be snoozed, scheduled and sorted by server-side filters, and your own domain connects with DKIM signing. The mail client is built in: messages link to records and are sorted by filters, and your own domain connects with DKIM.
A mail mockup with four tabs: a connected custom domain, a working inbox filter (change the conditions and matching messages light up; the button files them into a folder), a mailbox summary and domain diagnostics.
DNS records in place
Addresses on this domain
Applies to new mail arriving in Inbox — on the server, even when Mail is closed. The button below files messages already there.
Inbox
Talver-Agro
Bank
Flow by day
incoming outgoing
Awaiting reply
The summary is computed on the fly, for one mailbox or all of them at once; the period is 7, 30, 90 days or a year. Clicking a correspondent takes you to a search on their address.
Advice for this finding
“p=none” means the recipient sees the violations and does nothing about them. Raise the policy to quarantine once the reports show your own mail passes the checks.
Beyond the domain, the validator checks addresses (a live probe up to RCPT TO, without sending a message), scores a draft for spam from 0 to 10, and queries 28 blocklist zones. Every finding comes with advice.
A working mockup of a group chat: type a message and send it with Enter or the button; below, pick an order and send its card into the conversation.
The frame for ЗАК-0042 is welded — handing it over to assembly.
Record card
Pumping station NS-40
The client wants everything in one shipment, no follow-ups.
3 replies in thread
Record card
Oil station MS-250
Record card
Hydraulic cylinders for a bottling line
Record card
Press P-160 upgrade
Chat is built on Matrix: the chat server runs on the same installation, with federation and open sign-up turned off. Direct and group conversations, threads, polls, pinned messages and message search — and you can send a record card straight into a conversation. Direct and group conversations, threads and polls on the installation’s own chat server — and you can send a record card straight into a conversation.
Note. There are no voice or video calls. There’s no end-to-end encryption either: chat data stays on the installation’s server.
Company channels are connected under Channels → Messengers, and conversations arrive in the ordinary Chats section: with a channel badge, a queue and a response timer. Each client has one room for every request, so the history never breaks. Channel access is granted by role: read, work or configure. Messenger conversations arrive in the ordinary Chats section, with a channel badge, a queue and a response timer.
The demo is sped up: a second here is a working minute
A working mockup of the Chats section in Queue mode: client conversations from different messengers on the left, the open conversation on the right. You can take a conversation, snooze it, write an internal note or a reply; opening a conversation from another channel changes the rules of the message field.
Anna K.
writes to “Telegram · sales”
Looks like Talver-Agro — username matches (Telegram)
Hello! When does ЗАК-0042 ship? We need to book a crane for unloading.
Igor, will NS-40 make it by Sep 18? The client is booking a crane.
Yes. Welding is done, we ship on the morning of Sep 18.
Hello Anna! Pumping station NS-40 on ЗАК-0042 ships on Sep 18, in the morning. I’ll send the waybill right here.
Sent
Sent
Poll
Response timer
9 min passed Channel target — 15 min
Up to half the target the timer stays calm, up to the target it turns amber, after that red. It counts working minutes on the channel’s schedule: at night and on weekends it stands still, as it does for a snoozed conversation.
What the client gets
| Telegram | Instagram · Facebook | VK | ||
|---|---|---|---|---|
| Formatting | headings, tables, checklists, spoilers — as typed | bold, italic, strikethrough, code, quotes, lists | plain text, lists as “•” marks | plain text, lists as “•” marks |
| Poll | a native Telegram poll | the question with answer buttons | the question with answer buttons | the question with answer buttons |
| Reaction | from Telegram’s list; the client sees the latest | any; the client sees the latest | stays inside the team | stays inside the team |
| Quoted reply | goes out as a quote | goes out as a quote | a regular message, no quote | a regular message, no quote |
| Reply window | none | 24 hours, then approved templates only | 24 hours; a human reply for up to 7 days | none |
Open a conversation from another channel — the message field shows only what that messenger will pass on to the client.
| Channel | How it connects | What to know |
|---|---|---|
| Telegram | A company bot by token | Buttons, native polls, reactions and quoted replies; your own reply can be deleted on the client’s side within 48 hours |
| Telegram Business | A manager connects their business account to the company bot | Only the manager and people they grant access can see the conversations; AI only with the manager’s consent |
| The official Cloud API on the company’s keys | A 24-hour window: after it, approved templates only, including ones with an image or a document; delivery and read ticks | |
| VK | A community key | Buttons and a command menu; no window |
| Instagram and Facebook | The company’s Meta page and app | A 24-hour window; a human reply for up to 7 days |
A working mockup: the “Take a request” bot scenario leads a client conversation step by step — it validates the phone number, offers buttons, creates a record and hands the conversation over to an operator. Buttons switch the steps; Take over stops the bot.
Roman T.
Hello. I need a repair request for an NSh-32 pump.
Bot · “Take a request”
Let’s file the request. Leave a phone number and a technician will call you back.
Roman T.
Call me after lunch
Bot · “Take a request”
That doesn’t look like a phone number. Please type it in digits, for example +375 29 000-00-00.
Roman T.
8 029 000 00 00
Phone: +375 29 000-00-00 — accepted and normalized to +375…
Bot · “Take a request”
When is it convenient for the technician to come?
Roman T.
▸ Tomorrow
When to come: Tomorrow
Repair requests
ЗР-0031
The client is linked to the record
Bot · “Take a request”
Answers. Phone: +375 29 000-00-00. When to come: tomorrow.
In the queue
The team got the answers — the response timer started.
Note. Viber, MAX and personal accounts through unofficial bridges are not supported. An edit to a message already sent doesn’t reach the client, and there are no Telegram group chats. Text formatting is translated into each messenger’s own markup; where polls don’t exist, the client gets the question with buttons.
Sites is a visual builder for static websites. The platform generates plain HTML, CSS and JS and uploads them over SSH/SFTP to your hosting, so a published site keeps working even when Eyeward is off. A lead form and visitor chat go onto the site as widgets: submissions arrive in Widgets and by email, conversations go to operators in Chats. A visual builder publishes plain HTML, CSS and JS to your hosting — the site keeps working even if Eyeward is off.
Sites editor
13 block types, 3 breakpoints
HTML, CSS, JS
sitemap.xml, robots.txt, meta tags
Your hosting
the site runs without Eyeward
Visitor
lead form, chat
if the app is unreachable, collect.php on your hosting queues events, and they’re picked up once a minute
Eyeward
Widgets, Chats, email
Note. Eyeward doesn’t host sites: publishing goes to your own server. For forms and chat to work, the app needs a public address.
The bell shows two separate counters: notifications and unread chat messages. Changes and comments arrive only for records you follow with the Follow button; mentions and assignment events always arrive, and an assignee is subscribed to the record automatically. The bell and chat keep separate counts; changes and comments arrive for records you follow.
A working mockup of the bell panel. The Follow button on order ЗАК-0042 decides whether change and comment notifications arrive; the event buttons show what lands in the bell, and the channel switches decide whether a push goes out.
ЗАК-0042 Pumping station NS-40
Record changed10 min
ЗАК-0042 · Status
Confirmed In production
Mention1 h
ЗАК-0042: “@you, check the line items before assembly”
Assignment · due soon3 h
“Check the welds” — due Sep 11, 2026
In production Ready to ship
Try an event
What to send
The Solutions store lets you publish your modules for others and install theirs; everything in it is free. Installing creates an independent copy: the author can’t change yours, and a new version installs next to the old one. There are no public solutions in the catalog yet — for now the store is the mechanism for sharing your own modules. Publish your modules, install others’ — for free; an install is an independent copy. There are no public solutions in the catalog yet.
The solution takes a snapshot of the modules at submission time. It won’t go out while it references modules outside the package. The listing has a name, an icon, one of 10 categories, a Markdown description and screenshots.
A superadmin reviews the solution. New versions ship with a “What’s new” list; a solution can be hidden from the storefront or deleted.
Just me, or into a company you own. References to the author’s people, roles, companies, charts and files are reset on install.
A working mockup of installing a solution: choose where to install and press Install to see the install steps. Then release a new version as the author and see it install alongside, not over the top.
Order tracking v1.0
Orders and Clients modules, the relation between them, an “Invoice for payment” document, 20 sample records
New solution version · v1.1
What’s new: a Payment due field in Orders.
You’ll get an independent copy: 2 modules, 1 document, 20 sample records. The author’s future versions won’t touch it.
Installed by you
Note. An installed copy can’t be updated in place: a new version of the solution installs next to the old one.
The assistant panel opens on the right over any page (Mod+J) and knows what’s on your screen. You bring your own provider key: OpenAI, Anthropic, Gemini, OpenRouter, Ollama on your own machine or Ollama Cloud — no language model runs on the platform’s server. It reaches data under your session, so roles, hidden fields and module gates apply by themselves. The assistant panel (Mod+J) runs on your own provider key and sees data only within your roles.
The platform is an MCP server itself. Any MCP-compatible AI agent client connects with a token and acts on behalf of the token’s owner, within that person’s roles. Tokens are issued under Settings → Agents as Read only or Read and write; the token string is shown once, and revoking takes effect immediately. The platform is an MCP server: an external AI agent connects with a token and acts within the token owner’s roles.
| Access | Tools | Qty |
|---|---|---|
| Read | records, history and versions, mail, chat, assignments and notifications, free time in the calendar, files and their text, documents, charts, activity, companies and people, knowledge base, support | 33 |
| Write | create and update a record, a comment, an assignment, mark notifications — only with a Read and write token | 6 |
| Delete | There is no delete tool at all | 0 |
| Withheld | sending mail and chat messages, support, the assistant’s scheduled runs — these act outward and towards a live person, and an external client has nobody to confirm with | 7 |
The set holds 50 tools in total; an external agent gets 39. Transport: POST /mcp (Streamable HTTP, no sessions). Tool responses are cut at 100,000 characters; only a hash of the token is stored, and banning a user closes their tokens too.
A file sync client: two-way sync, and when there’s a conflict both versions are kept. Its token only opens the Files section. The web app installs on phones and computers as a PWA — it has no offline mode. Eyeward Sync syncs files both ways, and the web app installs on phones and computers as a PWA — with no offline mode.
| System | Build | Note |
|---|---|---|
| Windows x64 | .exe installer | Files on demand is in development |
| Linux x86_64 | AppImage, DEB, RPM, pacman | Files on demand works |
| Android | APK | No syncing of device folders |
| macOS, iOS | — | No builds yet |
97 keyboard shortcuts in 11 groups — reassign, disable or reset almost any of them. A light, dark or system theme, 20 ready-made color schemes plus up to 5 of your own, and a sidebar you arrange yourself: groups, icons, your own items. A light, dark or system theme, 20 ready-made color schemes plus up to 5 of your own; shortcuts can be reassigned.
A working mockup of the design settings. Pick a theme — light, dark or system — or a ready-made color scheme, and the whole app window recolors, just like in the product. The theme and the scheme are one choice.
Design
Customize the theme and create your own color schemes
A working mockup of the keyboard shortcut settings. While this window is hovered or focused, press a combination from the list and its row responds. Change records a new combination and checks it for conflicts; a fixed combination can only be turned off.
Hover over this window and press J, K, E, S or R — the row responds. Change assigns a combination of your own.
On a phone, shortcuts are read-only: assign new ones from a device with a keyboard.
Global
Press the keys. Esc and Enter are recorded too — leave with the buttons below (Tab).
Note. The English interface isn’t complete yet: the rule, status-transition, record-action and relation editors show Russian labels only.
Tell us what you want to build, and in a demo we’ll show how your process maps onto Eyeward’s modules, views and rules.