Sketch your process. Eyeward builds the system.
Orders and production, clients and inventory, a home renovation or the family budget. Describe what your process is made of — then run it as a table, a board, a Gantt chart, documents and charts. No programmers needed.
A manufacturing process drawing: client, order, production, shipment and invoice are linked. Order ЗАК-0042 turns into a record card, and a rule moves it to “In production”.
Pumping station NS-40
- Client
- Talver-Agro
- Amount
- 128,400.00 Br
- Delivery date
- Sep 18, 2026
- Shop
- Machining
A home renovation drawing: rooms, tasks, purchases, budget and photos. The task “Kitchen tiling” turns into a card; when a tile purchase is added to it, a rule moves the task to “In progress”.
Kitchen tiling
- Room
- Kitchen, 11.4 m²
- Estimate
- 1,850.00 Br
- Due
- Sep 26, 2026
- Contractor
- Sergei
A family budget drawing: accounts, expenses, categories, goals and a report. The expense “Weekly groceries” turns into a card and a formula recalculates what is left of the category limit.
Weekly groceries
- Category
- Groceries
- Amount
- 186.40 Br
- Date
- Sep 14, 2026
- Account
- Card
Every system is built from three layers
You describe the structure, fill it with data and choose how to show it. A factory’s order book works this way, and so does a flat renovation.
-
Structure
A module describes one thing in your process: an order, a client, a machine, an expense. You add fields from the palette and lay the form out in tabs, sections and columns.
-
Data
Every record is a card built on that form. It keeps a version history you can roll back, comments with @mentions, its own files and assignments with due dates. Two people can edit one record at once: only the fields you changed are saved.
-
Display
The same records show up as a list, a kanban board or a Gantt chart, fill Word and Excel document templates and feed charts. Roles decide who sees and edits what, down to a single field.
Drawing: three layers of the Orders module. Bottom: the module’s fields — Name, Client (relation), Status, Delivery date (date), Order total (currency), Discount (percent), Urgent (checkbox). Middle: records ЗАК-0042 to ЗАК-0047 with statuses and comment and file counts. Top: a kanban board by status, an Invoice document in DOCX, a chart and roles.
A form is assembled from the field palette
The palette holds 34 types in five categories. Each has its own settings: a number takes a unit and digit grouping, a phone number a Belarus or Russia mask, and a select pulls its options from seven sources, from a custom list to the company’s employees.
Field palette · 34
Basic17
- Text
- Textarea
- Number
- Checkbox
- Date
- Datetime
- Time
- Time range
- Duration
- Phone
- Password
- Code
- Currency
- Percent
- Color
- Rating
Choice2
- Select
- Status
Relation5
- Relation
- Record card
- Rollup
- Stage rollup
- Row status
Advanced8
- Table
- Row dependencies
- Progress
- Chart
- Attach
- Attach Image
- JSON
- Button
System2
- Heading
- Divider
The Title field is built in: every module has one, so it isn’t in the palette.
- Nametype: built-in
- Pumping station NS-40
- Clienttype: Relation
- Talver-Agro
- Statustype: Status
- In production
- Delivery datetype: Date
- Sep 18, 2026
- Order totaltype: Currency
- 128,400.00 Br
- Discounttype: Percent
- 5%
- Urgenttype: Checkbox
- Yes
- Line itemstype: Table
-
Item Qty Price Total NSh-40 pump 4 18,600.00 74,400.00 R-80 directional valve 6 6,800.00 40,800.00 1SN DN12 hydraulic hose 20 660.00 13,200.00
Same records, many views
Ten Gidrovelm orders, one set of records. Switch the view and rows turn into cards, cards into Gantt bars, bars into calendar events, and the amounts stack up into a chart. Nothing gets copied, and the records stay exactly as they were.
What this view can do
List
- Pick, reorder and rename columns; click a header to sort, with three states.
- Quick filters sit above the list, and the condition builder adds AND/OR groups and 12 operators. A good filter can be saved as personal or global.
- Select all records to change one field across the whole selection at once, or generate documents for exactly that selection.
Kanban
- Columns come from a field: a status, a select or a checkbox. Records without a value get a column of their own.
- Drag a card to the next column and the field changes; the edit lands in the version history, marked “Kanban”.
- You choose which fields a card shows, and whether cards follow the system order or a number field. Each column loads 30 cards at a time.
Gantt chart
- Six scales, from minutes to quarters, and up to 2,000 records on the canvas.
- Drag a bar to move it, pull an edge to stretch it. Each gesture is an ordinary record edit, so it shows up in the version history, the activity center and notifications.
- Durations count working days, with the chosen country’s public holidays and your own days off. The work log draws actual time down to the minute.
Calendar
- A calendar has no events of its own: it shows the records of the view’s modules as layers, each in its own color. There are six modes, from month and week to agenda and resources.
- Move an event to another day or stretch it, and the record’s dates change — the same way as on the Gantt chart. A new record starts from a free slot.
- Participants get reminders; an overlap on a resource is highlighted, but double-booking isn’t forbidden. Events reach your phone’s calendar through an .ics subscription.
Chart
- Charts are a separate section, not a view: 37 types in 6 groups, from column charts to Sankey diagrams.
- They read the same module records: 7 aggregates, up to 5 metrics, grouping by day, week or month, and filters from the same condition builder.
- A finished chart goes onto a workspace as a block, or right into a record card as a Chart field.
Relations and automation carry an order from client to shipment
Clients, orders and production stages are separate modules joined by relations. Transitions change statuses, formulas and rollups keep amounts and progress current, and the invoice comes from a template. All of it is module settings, not code.
-
Clients КЛ-0001 Talver-Agro
The order starts on the client’s record
A “New order” button creates ЗАК-0042 already linked to Talver-Agro. Nobody retypes the client: the order links to the client’s record, and the client’s Relations tab lists every order they have.
Record action · 4 types
“New order” → “Create linked record”
relation Clients → Orders
-
Orders ЗАК-0042
A formula works out the amount due
The manager enters three line items and a 5% discount, then confirms the order. A “Set value” rule recalculates the amount on every edit: field references in curly braces and 17 functions, no programming.
Rule · 9 actions
= round(sum({items.amount}) * (1 - {discount} / 100), 2)
121,980.00 Br
-
Production ПР-0101…ПР-0103
A stage appears, and the order is “In production”
The foreman adds the stages: cutting, frame welding, assembly. The first one alone sets ЗАК-0042 to “In production” — nobody touched the order itself.
Status transition · 2 triggers
When a record is created in Production
If: always → “In production”
-
Production → Orders 3 stages
Stages close, and progress keeps count
Rollups on the order count the stages, all of them and the finished ones, and a rule turns that into a percentage. When the last stage closes, a transition sets “Ready to ship” — and the version history credits the status engine.
Rollup · 5 aggregations
Stages done = Count where Status = “Completed”
0 unfinished → “Ready to ship”
-
Documents Invoice
The invoice comes from a template
The Document button on the record hands you a Word file: the order’s fields, line items looped from the table, the amount in words. The template is built in a visual editor; you print from Word, Excel or LibreOffice.
DOCX template · 42 functions
{{ amount_words(amount, 'BYN') }}
Сто двадцать восемь тысяч четыреста рублей 00 копеек (the amount in words, in Russian)
-
Orders notifications
Shipped, and everyone following knows
The warehouse sets the status to “Shipped”. Everyone who clicked FOLLOW on ЗАК-0042 gets a notification in the bell, and on their phone too if push is on.
Notifications · 8 push channels
Record updated
Ivan edited a record in Orders
Pay for the system, not for a consultant’s hours
A system built around your process is usually bought twice: the license, then the implementer’s work — and then again for every change. In Eyeward, setup is part of the product. Describe your business in plain words: the assistant in Constructor mode assembles a project, and you review the drawing and deploy it with one button.
Assistant
Constructor · Tracking for a car service
Set up tracking for a car service: clients, vehicles, work orders with labor and parts, payments. A mechanic sees only their own work orders and must not see the discount.
Think deeper- Plan
- Reading how the platform is set up
- Reading the builder guide
- Starting a project
- Editing the project
- Editing the project
- Editing the project
- Editing the project
- Editing the project
- Reading the project
- Editing the project
- Preparing the project deployment
- Check passed
I’ve assembled the “Car service” project and checked it. Nothing has been created in the running system yet — it all appears when you click Apply.
6 modules · 28 fields · 6 relations · 1 document
After install, the same button also creates
- Chart: Revenue by month · from “Payments”
- Workspace: Service · 6 blocks
- Role: Mechanic · 1 field hidden · own records only: Work orders
You can undo the deployment with one button for 7 days — as long as nobody adds records to the new modules, changes what was installed or assigns people to the roles.
Project “Car service”
Draft revision 6Project schema. Modules: Clients, Vehicles, Work orders, Labor, Parts, Payments. Relations: Clients → Vehicles; Clients → Work orders; Vehicles → Work orders; Work orders → Labor; Work orders → Parts; Work orders → Payments.
No modules yet
The assistant adds them as you talk — the schema grows right here.
- comes through a relation
- formula
- rollup over related records
- in use
{rat}: no such field. Module fields: hours, rate, cost modules.works.fields.cost fixed: {hours} * {rate}
Project check: no problems
Draft — nothing in the running system has changed
Menu
- Chats
- Files
Modules — appear after deployment
- Clients
- Vehicles
- Work orders
- Labor
- Parts
- Payments
Project “Car service” — contents
- Modules6
- Clients, Vehicles, Work orders, Labor, Parts, Payments
- Relations6
- the client’s phone and the VIN flow into the work order
- Logic—
- statuses with conditional transitions, a labor cost formula, a Total rollup over labor and parts
- Views3
- list, a board of work orders, a Gantt chart of labor
- Document1
- Work order with labor and parts tables
- Analytics2
- a Revenue by month chart, a Service workspace
- Role1
- Mechanic: own work orders only, discount hidden
Assistant
Constructor · Make-to-order manufacturing
Set up make-to-order manufacturing: clients, products, orders, and jobs by work center with planned and actual time. Jobs go on a Gantt chart; a worker sees only their own.
Think deeper- Plan
- Reading how the platform is set up
- Reading the builder guide
- Starting a project
- Editing the project
- Editing the project
- Editing the project
- Editing the project
- Editing the project
- Reading the project
- Editing the project
- Preparing the project deployment
- Check passed
I’ve assembled the “Manufacturing” project and checked it. Nothing has been created in the running system yet — it all appears when you click Apply.
4 modules · 22 fields · 3 relations · 1 document
After install, the same button also creates
- Chart: Actual time by work center · from “Jobs”
- Workspace: Manufacturing · 5 blocks
- Role: Foreman
- Role: Worker · own records only: Jobs
You can undo the deployment with one button for 7 days — as long as nobody adds records to the new modules, changes what was installed or assigns people to the roles.
Project “Manufacturing”
Draft revision 6Project schema. Modules: Clients, Products, Orders, Jobs. Relations: Clients → Orders; Products → Orders; Orders → Jobs.
No modules yet
The assistant adds them as you talk — the schema grows right here.
- comes through a relation
- formula
- rollup over related records
- in use
{plan_mn}: no such field. Module fields: center, start, end, plan_min, fact_min modules.jobs.fields.deviation fixed: {fact_min} - {plan_min}
Project check: no problems
Draft — nothing in the running system has changed
Menu
- Chats
- Files
Modules — appear after deployment
- Clients
- Products
- Orders
- Jobs
Project “Manufacturing” — contents
- Modules4
- Clients, Products, Orders, Jobs
- Relations3
- the product’s unit flows into the order, the order’s due date into every job
- Logic—
- order and job statuses, a plan-vs-actual deviation formula, an order progress rollup over jobs, a task for the foreman a day before the due date
- Views4
- a Gantt chart and a board of jobs, a board and a calendar of orders
- Document1
- Route sheet with a table of jobs
- Analytics2
- an Actual time by work center chart, a Manufacturing workspace
- Roles2
- Foreman and Worker: a worker sees only their own jobs
Assistant
Constructor · CRM: from lead to payment
Set up a CRM: leads from the website, clients, deals with stages, line items for a quote, and payments in installments. A sales rep sees only their own deals.
Think deeper- Plan
- Reading how the platform is set up
- Reading the builder guide
- Starting a project
- Editing the project
- Editing the project
- Editing the project
- Editing the project
- Editing the project
- Reading the project
- Editing the project
- Preparing the project deployment
- Check passed
I’ve assembled the “Sales” project and checked it. Nothing has been created in the running system yet — it all appears when you click Apply.
5 modules · 27 fields · 4 relations · 1 document
After install, the same button also creates
- Chart: Pipeline · from “Deals”
- Chart: Revenue · from “Payments”
- Workspace: Sales · 6 blocks
- Role: Sales rep · own records only: Deals, Leads
- Role: Accountant
You can undo the deployment with one button for 7 days — as long as nobody adds records to the new modules, changes what was installed or assigns people to the roles.
Project “Sales”
Draft revision 6Project schema. Modules: Clients, Leads, Deals, Deal items, Payments. Relations: Clients → Deals; Leads → Deals; Deals → Deal items; Deals → Payments.
No modules yet
The assistant adds them as you talk — the schema grows right here.
- comes through a relation
- formula
- rollup over related records
- in use
line 3: the document has no “cliet”. Similar: client documents.quote.dsl fixed: {{ client }}
Project check: no problems
Draft — nothing in the running system has changed
Menu
- Chats
- Files
Modules — appear after deployment
- Clients
- Leads
- Deals
- Deal items
- Payments
Project “Sales” — contents
- Modules5
- Clients, Leads, Deals, Deal items, Payments
- Relations4
- the client’s name flows into the deal, the source comes from the lead
- Logic—
- a pipeline of stages, “no win without an amount”, a Paid rollup and a balance formula, Create deal and Add payment buttons
- Views3
- a board of deals, a board of leads, a calendar of payments
- Document1
- Quote with a table of line items
- Analytics3
- Pipeline and Revenue charts, a Sales workspace
- Roles2
- Sales rep: own deals and leads only; Accountant
What an implementer usually does — and what does it here
In Eyeward: A project in Constructor mode: the drawing of modules and relations is on screen before anything is created, and the project check names its errors in plain words.
1 problem blocks deploying the project. The assistant usually fixes these itself as it works.
{rat}: no such field. Module fields: hours, rate, cost modules.works.fields.cost
Labor · the Cost field = {hours} * {rat}
In Eyeward: Rules with formulas, status transitions, rollups, record buttons and task automations are settings, not code. The assistant drafts a rule as a card and runs it against your records: “now → after”.
Always applies
Discounted amount = {Amount} * (1 - {Discount} / 100)
Checked on records: applies to 3 of 3
| Record | Discounted amount |
|---|---|
| ЗАК-0050 | —134,710.00 |
| ЗАК-0048 | —54,912.00 |
| ЗАК-0047 | —284,115.00 |
Return the module settings to the version before this change? If they were changed after the assistant, undo won’t run.
When: Discount > 10
Blocks saving: “Get the director’s approval for a discount above 10%”
Checked on records: applies to 1 of 3
| Record | Discount | Result |
|---|---|---|
| ЗАК-0050 | 5% | doesn’t apply |
| ЗАК-0048 | 12% | Won’t save |
| ЗАК-0047 | 7% | doesn’t apply |
Return the module settings to the version before this change? If they were changed after the assistant, undo won’t run.
In Eyeward: The assistant writes the quote, invoice or certificate template itself and shows a trial print on a real record.
DOCXPer record
Modules: Orders
Test print on record ЗАК-0042 «Pumping station NS-40»
Invoice No. ЗАК-0042
Bill to: Talver-Agro, Pinsk
Delivery date: Sep 18, 2026
| Item | Amount | Discount | Due |
|---|---|---|---|
| Pumping station NS-40 | 128,400.00 | 5% | 121,980.00 |
Total due: 121,980.00 Br
Print warnings: 1
line 4: {{ contract }} — the Contract field is empty on this record
Stays a draft: only template editors can print it until it is published.
Return the document template to its state before applying (delete a created one)? If it was printed or changed, nothing will be undone.
In Eyeward: A role arrives as a “who sees what” card: how many records open to an employee before and after, with any widening of access called out.
Role of the company “Gidrovelm”
Access becomes wider — check the marked items below before applying.
Modules · 1
Orderswider
| Before | After | |
|---|---|---|
| Access | View only | View and edit |
| Level | 40 | 40 |
| Records | All records | Only where Manager = current user (view, edit) |
| Visible to Anna Kovaleva | 10 of 10 | 3 of 10 |
| Visible to Igor Savchuk | 10 of 10 | 4 of 10 |
- Discount read-only hidden
- Delivery date read-only editable
Hidden fields: 1
People with this role · 2
Anna Kovaleva · Igor Savchuk
Return the role to its state before applying (delete a created one)? If it was changed or already has people, nothing will be undone.
In Eyeward: The same panel: “add a field”, “don’t move to Won without an amount”, “show it as a board”. A card, a preview, Apply — no change-request contract.
Kanbannew
- Columns by field
- Status
- Card fields
- Client, Amount, Delivery date
Records by “Status” — 10 in total
- Draft1
- Confirmed2
- In production3
- Ready to ship2
- Shipped2
Return the view to its state before applying (delete a created one)? If it was changed or filters and calendar links were added, nothing will be undone.
In Eyeward: An applied card keeps an Undo button for 7 days; every module has a settings history you can roll back to any version.
When: Discount > 10
Blocks saving: “Get the director’s approval for a discount above 10%”
Return the module settings to the version before this change? If they were changed after the assistant, undo won’t run.
Settings history of the “Orders” module
- Version 15restored from version 13Current
- Version 14 rules · assistant Current
- Version 13 fields and form
- Version 12 statuses
Every saved module setting becomes a version: what changed, who changed it and when. Any version can be restored.
The assistant runs on your own language-model key: you pay the provider for tokens, not a contractor for hours. Without the assistant, everything above is assembled by hand in visual builders — there is no code either way. Constructor mode doesn’t yet create table fields inside a record or messenger broadcasts; those are added in the same settings.
Mail, chat, files and search, in the same window as your records
A client’s email shows up on the Mail tab of their record, the contract sits in the record’s folder and opens right in the browser, and search finds an order from one word in a comment. The specification lists the rest of the workspace.
A mockup of the Eyeward window: the section menu on the left — Dashboard, Orders, Clients, Chats, Mail, Files and System → Documents; in the middle, the “Invoice” template in the document builder, with order fields as {{ … }} placeholders and a table row that repeats over the order’s line items; on the right, the Data panel with record fields, related records, collections and company requisites. The Preview button shows the document built from order ЗАК-0042.
{{ company.legal_name }} Gidrovelm LLC
Invoice No. {{ meta.id }} ЗАК-0042
Order: {{ title }} Pumping station NS-40
Payer: {{ client.title }} Talver-Agro
Delivery date: {{ due_date }} 18.09.2026
| No. | Item | Qty | Amount |
|---|---|---|---|
| {{ index }} 1 | {{ item.item_name }} Pump NSh-40 | {{ item.item_qty }} 4 | {{ item.item_sum }} 74 400,00 |
| 2 | Directional valve R-80 | 6 | 40 800,00 |
| 3 | Hose RVD 1SN DN12 | 20 | 13 200,00 |
Row 2 repetition
Collection (source)items
Variableitem
Total: {{ amount }} 128 400,00 Br
Director ______ {{ company.director_name }} Astapenko P. I.
A mockup of global search (Ctrl K) over the order list: the query “pump”, the Include toggles below it — modules, comments, chats, mail, files — and results grouped under the Orders module, then chats, mail and files. The sparkle button at the end of the field turns on semantic search: a record found by meaning appears below the exact matches. The toggles and the sparkle are clickable.
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
- Pump NSh-32, emergency replacement 3d ago
- Pumping station NS-40 5h ago
- Hydraulics for a grain dryer 1d ago
- Oil station MS-250 by meaning 12d ago
- Anna Kovaleva · Production The NSh-40 pump for NS-40 is in stock, moving it to assembly 1h ago
- NSh-32 pump replacement: act and invoice Lemvara-Moloko · Please invoice the emergency pump replacement 2d ago
- NSh-40 pump datasheet.pdf Gidrovelm 4d ago
DNS zone for gidrovelm.example
Tick the records you’ve already published at your DNS provider, then press Verify.
DNS records in place DKIM signing is active — mail from this domain passes recipients’ checks.
- Ownership Found
- Mail routing (MX) Found
- SPF Found
- DKIM Found
- DMARC recommended Found
The full specification: 11 items
| Item | Section | What’s inside | Notes |
|---|---|---|---|
| 1 | Your own domain with DKIM signing, threads, Snoozed, scheduled sending, custom folders and filters that run on the server. A client’s emails show up on the Mail tab of their record. A mailbox summary, a validator for addresses and domains, and delivery status per recipient. | The platform can set up the domain’s DNS through your provider; bring existing mail over IMAP — once, or keep it syncing. | |
| 2 | Chat | Built on Matrix: direct and group conversations, threads, polls, pins, search. Share a record card straight into a conversation. | The chat server runs on the same installation. No calls or video. |
| 3 | Messengers | Clients write on Telegram, WhatsApp, VK, Instagram or Facebook — your people answer from the same Chats section. A conversation queue with a response timer, quick replies, broadcasts and message sequences, bot scenarios, and a client directory that records where each client came from. More | Channels connect with your company’s own keys. WhatsApp, Instagram and Facebook apply the platform’s 24-hour window. |
| 4 | Assignments | A task on a record, an email, a conversation or on its own: a checklist, stages that hand over to the next assignee, tags, a board. Task automations create them for you — on an event, on a date in a record or on a schedule. | A rule acts on behalf of the person who created it, within their permissions. |
| 5 | Files | Preview in the browser: office documents, text and code, images, video, archives, 3D and CAD — 25 formats, from STL to STEP and IFC. Office files are edited in ONLYOFFICE, together if you like, and every file keeps versions you can compare. | Only files have a trash bin. Download links can carry a password, an expiry date and a limit. |
| 6 | Documents | DOCX and XLSX templates in a visual builder: record fields, linked records, loops over line items and 42 functions, from amounts in words to grouping. | The output is a Word or Excel file. There’s no PDF export. |
| 7 | Sites | A page builder with 13 block types, plus Form and Chat widgets: leads arrive in Widgets and by email, conversations go to operators in Chats. | Sites are published over SSH to your own hosting and keep running even when Eyeward is off. |
| 8 | Search | Ctrl K searches records, comments, chats, mail and files; semantic mode matches a phrase by meaning. A calculator and exchange rates work right in the search bar. | Rates come from the Bank of Russia, the National Bank of Belarus and the ECB. Meaning is computed by an Ollama machine on the installation owner’s network. |
| 9 | Notifications | The bell collects edits and comments on records you follow, mentions and assignments. Push to the browser and phone over eight channels. | On iPhone and iPad, push works once the app is added to the Home Screen. |
| 10 | Assistant | A conversation with your own model, in a panel over any page: OpenAI, Anthropic, Gemini or Ollama on your own machine. It reads data under your session, shows an edit as a “before → after” card, creates and edits office files, and in Constructor mode assembles a system from a description. More | The provider key is yours — no language model runs on the platform’s server. |
| 11 | Eyeward Sync | Keeps company files up to date on your computer: two-way sync, and on a conflict both versions are kept. Download | Windows, Linux and Android (Android doesn’t sync device folders), version 0.1.3. There are no macOS or iOS builds. |
AI agents work with your data
Eyeward works as an MCP server itself. Connect Claude Code or another MCP client with a token: the agent reads your modules, searches and filters records and, with write access, creates and edits them. Always on your behalf, and within your roles.
Connect
claude mcp add --transport http eyeward https://<your-eyeward-address>/mcp --header "Authorization: Bearer eyw_mcp_(the rest of the token is hidden)"
Settings → Agents gives you this command with the token. This token is read-only.
-
You
What’s in production right now, and what ships first?
-
The agent calls the tool list_modules
-
Eyeward returns: Orders, Clients, Production…
-
The agent calls the tool get_module_schema Orders
-
Eyeward returns: Title, Client, Status, Delivery date, Order amount, Urgent…
-
The agent calls the tool query_records Orders · Status = “In production” · by delivery date ↑
-
Eyeward returns: 3 records: ЗАК-0042, ЗАК-0047, ЗАК-0050
-
The agent calls the tool get_record ЗАК-0042
-
Eyeward returns: Talver-Agro · 128,400.00 Br · urgent · link to the record
-
Agent
Three orders are in production, worth 575,700.00 Br. ЗАК-0042 “Pumping station NS-40” for Talver-Agro goes first: it’s due Sep 18, 2026 and marked urgent. Then ЗАК-0047 “Press P-160 upgrade” (Sep 30, 2026) and ЗАК-0050 “Hydraulics for a grain dryer” (Oct 16, 2026).
-
You
Move ЗАК-0042 to “Ready to ship”.
-
The agent calls the tool whoami
-
Eyeward returns: read_only · “Read-only token: creating and editing records is unavailable.”
-
Agent
I can’t: this token is read-only, so I have no write tools. Change the status in the record yourself, or issue a read-and-write token.
Eight tools out of thirty-nine
Eight tools out of thirty-nine
-
call whoami
returns mode: read_write · “Reading, creating and editing records are available, within this user’s role permissions. There is no delete.” mode: read_only · “Read-only token: creating and editing records is unavailable.”
-
call list_modules
returns Orders, Clients, Production…
-
call get_module_schema Orders
returns Client — relation to Clients · Status — 5 options · Delivery date — date · Order amount — number…
-
call query_records Orders · Status = “In production” · by delivery date ↑
returns total: 3 · ЗАК-0042, ЗАК-0047, ЗАК-0050
-
call get_record ЗАК-0042
returns “Pumping station NS-40” · Talver-Agro · 128,400.00 Br · url — a link to the record
-
call search “pump”
returns Orders: ЗАК-0042 “Pumping station NS-40”, ЗАК-0049 “Pump NSh-32, emergency replacement” · match: field
-
call create_record Orders · Client = Brevel-Stroy · Title = “Hydraulic cylinders for a loader”
returns ЗАК-0052 — numbered by the module’s template; the relation label and derived fields filled in automatically
-
call update_record ЗАК-0042 · Status = “Ready to ship”
returns record saved · module rules and rollups recalculated · a new version in the history
- create_record, update_record — not on this token.
These are the eight core tools; the set holds 39 — plus mail, chat, assignments and notifications, the calendar, files with their text and documents, charts, record versions, the knowledge base and support. The writing ones exist only for a read-and-write token: for a read-only token the server doesn’t register them at all. There is no delete tool at all.
How access works
How access works
- Tokens are issued only from the browser, in Settings → Agents. An agent can’t issue itself another one.
- The token string is shown once; only its hash is stored. Revoking works immediately, and banning a user closes their tokens too.
- The agent calls the same REST routes as the browser, so roles, rules and record versions apply to it exactly as they do to a person.
Sketch out your own life, too
The same modules, fields, relations and views work for personal life, too: a family budget, a renovation, a course of study, a collection. Eyeward has no ready-made “personal” templates — the six sheets below are setups you build yourself.
A module with no company is visible only to you.
Family budget
Diagram: Accounts, Categories and Expenses modules. An account and a category each have many expenses. A category has a limit, a Spent rollup and a Left formula.
- A rollup adds up the category’s expenses.
- A formula works out what’s left: limit minus spent.
- A pie chart of spending by category.
Home renovation
Diagram: Rooms, Tasks and Purchases modules. A room has many tasks, a task has many purchases. Every task has a Files tab with photos and estimates.
- Photos and estimates sit in each task’s Files tab.
- A dependency: tiling comes after the wiring.
- A Gantt chart of the tasks.
Study
Diagram: Courses, Lectures and Homework modules. A course has many lectures, a lecture has many homework items.
- Lecture notes go in the record’s Markdown notes.
- Drag a card to move it to the next column.
- A homework kanban on the Status field.
Vinyl collection
Diagram: Artists, Shelves and Albums modules. An artist and a shelf each have many albums. An album has a cover, a year and a rating.
- The cover is an Image field, so the list shows a thumbnail.
- The rating shows as stars right in the row.
- A list of albums with covers.
Trips
Diagram: Trips, Bookings and Expenses modules. A trip has many bookings and expenses. A trip has a budget and the share already spent.
- A rollup and a formula show how much of the budget is gone.
- The list shows it as a progress bar.
- A list of trips.
Habits
Diagram: Goals, Habits and Check-ins modules. A goal has many habits, a habit has many check-ins. A scheduled action creates the check-ins by weekday.
- A scheduled action creates check-ins on the weekdays you pick.
- A rollup counts the completed check-ins.
- A calendar heatmap shows the streak.
All your data on one server
The database, files, search, mail, chat and office editor run on the server of whoever owns the installation — not in someone else’s cloud. Very little leaves it, and everything that does is named below.
- Browser and PWA
- Eyeward Sync
- AI agent over MCP
Sign-in
Password, two-factor sign-in with TOTP and one-time backup codes, QR sign-in. A list of your sessions, where you can end any other one.
Tokens
The sync client gets files only; an AI agent gets read or read-and-write. A token is shown once and the database keeps only its hash. A ban closes every way in, tokens included.
Access
Access comes only from company roles: levels 1–100 on modules and fields, 11 operations, “own records only” conditions. The server checks the rights, and any role can be previewed through an employee’s eyes in read-only mode.
Services
Application (API and real time), Background jobs (indexing and mail-outs), Database (records and settings), Cache (job queues), Search (full text), Search (by meaning), Chat (a Matrix server), Mail (its own server), Office (documents and sheets).
- ApplicationAPI and real time
- Background jobsindexing and mail-outs
- Databaserecords and settings
- Cachejob queues
- Searchfull text
- Searchby meaning
- Chata Matrix server
- Mailits own server
- Officedocuments and sheets
Chat doesn’t talk to outside servers: federation and sign-up are off, and the only way in is through Eyeward.
Data
Files sit on the server’s disk. The activity log outlives deleted records; versions cover records, module settings, documents, charts, workspaces and file contents.
What leaves the server
Plus whatever you send yourself: email to outside recipients, IMAP mail import, and site publishing over SSH to your own hosting.
Modules, records and roles in every plan
Plans differ in how many people the company has and how much storage its data gets; on top come analytics, mail on your own domain, sites and semantic search.
Eyeward plans: monthly price, number of people, storage and what is included
Pick a plan and the rows show what it includes. Start: 1 person in the company, 2 GB of storage. Includes modules, records, views and roles. From Team: analytics and charts, mail on your own domain. From Business: sites, semantic search.Team: up to 25 people in the company, 500 GB of storage. Includes modules, records, views and roles; analytics and charts; mail on your own domain. From Business: sites, semantic search.Business: up to 100 people in the company, 2 TB of storage. Includes modules, records, views and roles; analytics and charts; mail on your own domain; sites; semantic search.Corporate: no cap on people, from 2 TB of storage. Includes modules, records, views and roles; analytics and charts; mail on your own domain; sites; semantic search.
A line starts at the plan where a feature appears and carries on through the larger plans.
Prices are in Belarusian rubles (Br) per month. Plans are connected on request: in-app payment isn’t available yet.
See Eyeward on your own process
Tell us in the request how your work runs today and how many people are involved. We’ll get in touch, find a time and show you Eyeward on an example of your own process.
Already using Eyeward? Sign in