No-code enterprise business platform
Let standard work come in ready-made modules. The processes that set you apart — data structures, approval steps, permissions and reports — you define yourself, without writing code.
In the cloud or on your own servers · Turkish, English, German · Web and mobile
You win because your processes differ from your competitors’. In most systems, though, every difference becomes a change request, and every request becomes a wait.
| Packaged software | Custom-built software | MitosOne | |
|---|---|---|---|
| Day one | You start quickly. | You start months later. | You start quickly with ready-made modules. |
| First custom requirement | “The package doesn’t do that.” The process bends to the software. | New analysis, new quote, new wait. | Defined in the interface, the same day. |
| Permissions, audit log, mobile, API | Whatever the package provides. | Each one is rebuilt. | Ready automatically for every new record type. |
| Year three | The exceptions have moved to Excel. | The know-how has left with the team. | Every change is versioned and can be rolled back. |
MitosOne Studio
From record types to screens, from processes to documents, from external connections to permissions — everything is built in Studio, without writing code. The menu on the left follows the groups of the Studio menu in the product; as you scroll, the screens open one by one.
01 / 24 · Getting started
You describe your work in your own words; the assistant asks about what’s missing to clarify it and proposes a step-by-step setup plan. Each step is set up only once you approve it.
02 / 24 · Data
You build your company’s record types: 19 field types, relations, subtables for line items, and calculated fields using a formula language with 43 functions.
03 / 24 · Data
You import an Excel (xlsx) or CSV file with a preview; a record whose key field matches is updated instead of a new one being created. The “App from Excel” wizard builds the record type, screens and menu from the file in one go.
04 / 24 · Interface
For each record type you choose from 11 view types: list, form, detail, kanban, calendar, gallery, timeline, pivot, chart, dashboard and process diagram. Long forms are split into tabs.
05 / 24 · Interface
You build management dashboards on a drag-and-drop grid: 30 chart types, KPI tiles, an event calendar.
06 / 24 · Interface
You build reports with an Excel-like pivot and send them to the right people at a time you choose; each report goes out as both Excel and PDF.
07 / 24 · Interface
You build the menu your users will see: groups, headings, ordering.
08 / 24 · Logic
You build processes on a visual canvas with 26 nodes: trigger, condition, loop, create and update record, approval, email, document generation, external service call.
09 / 24 · Logic
For each role you choose the record scope: own records, the department’s, or all; the scope can be narrowed by stage. Where needed, you refine it with row and field rules.
10 / 24 · Output
You design documents such as quotes, contracts and delivery notes with a drag-and-drop PDF layout or your company’s Word template; you can also start from a sample Word or PDF document you already have.
11 / 24 · Outside world
External systems live on a single screen. With the REST API and outgoing webhooks you notify them; with incoming webhooks they write to you instantly; ready-made connections are set up with a wizard.
12 / 24 · Outside world
You publish application and request forms that need no sign-in; every submission becomes a record.
13 / 24 · Outside world
You invite your customers and suppliers to the portal; a company’s portal administrator can also invite their own employees.
14 / 24 · Publishing
Every publish in Studio is a version; the difference between two versions is compared on screen.
15 / 24 · Publishing
You open a test copy of your company with one click; in the sample data copied from live, personal and encrypted fields are masked. A change that is ready goes live with four-eyes approval at the time you schedule, and can be rolled back within 30 days.
16 / 24 · Publishing
Who changed which value to what, and when: all of it is recorded.
17 / 24 · Advanced tools
You define lists such as “Status”, “Priority” and “Region” once and use them in several fields.
18 / 24 · Advanced tools
You connect to REST and SOAP services without code; connection details are kept in an encrypted vault.
19 / 24 · Advanced tools
You define your business days and public holidays; durations run on business days, not calendar days.
20 / 24 · Advanced tools
You draw P&ID-style process diagrams with pipe, valve, pump, compressor, tank and instrument symbols, and link the symbols to your records. Values refresh automatically as records are written; when a limit is exceeded, the symbol is marked with a warning or alarm frame and an alarm record is created. You embed the diagram in dashboards, record pages and PDF documents.
21 / 24 · Advanced tools
You start with 28 ready-made symbols and can upload your own SVG symbols too. On upload, scripts, external links and styles are stripped.
22 / 24 · Advanced tools
You define your record type and field names in Turkish, English and German.
23 / 24 · Advanced tools
You build custom pages made of summary figures, lists, charts and buttons.
24 / 24 · Advanced tools
You set the layout of the page shown when a record is opened: fields, related records and charts.
“Sample Request”, “Site Visit”, “Mould Card” — whatever exists in your business exists in the system too. When you define a record type, MitosOne creates a real database table behind it; not a bag of custom fields.
| Field | Type | Definition |
|---|---|---|
| talep_no | sequence no | NT-{YYYY}-{0000} · automatic |
| cari | relation | → Account many-to-one |
| talep_tarihi | date | required |
| termin | calculated | WORKDAYS(talep_tarihi, 5) using the public holiday calendar |
| kalemler | subtable | Sample Item 1–50 rows |
| toplam_adet | rollup | SUM(kalemler.adet) |
| segment | lookup | cari.segment |
| sorumlu | user | default: creator |
| ek_dosya | file | pdf, dwg |
AI-assisted setup assistant
The setup assistant listens to what you want to build in your own words, clarifies the gaps with questions and proposes a step-by-step setup plan. No step is set up without your approval.
We want to track expense requests and their approvals. Anything over 5.000 ₺ should go to the general manager.
Which manager should expenses go to for approval — the requester’s department manager?
Why I’m asking: to route the approval to the right person.Approval stages define which state a record moves to from which, by whom and under what condition. The visual workflow runs what happens at each transition: it requests approval, generates documents, sends notifications.
Stage history
Workflow nodes · 26
Hiding a menu is not security. In MitosOne, row and field rules go inside the query: the same list, the same report and the same API response return only as much data as the person opening it should see.
bolge == user.bolge
Field rule
maliyet → read: finance · other roles: masked
| Order | Account | Region | Amount | Cost |
|---|---|---|---|---|
| SIP-0418 | Ege Tekstil | Ege | 1.245.000 | |
| SIP-0419 | Marmara Lojistik | Marmara | 96.750 | |
| SIP-0420 | İzmir Ambalaj | Ege | 212.400 | |
| SIP-0421 | Anadolu Makina | İç Anadolu | 418.500 | |
| SIP-0422 | Bursa Otomotiv | Marmara | 762.900 | |
| SIP-0423 | Konya Gıda | İç Anadolu | 33.200 |
2 / 6 records The same rule applies in lists, pivots, dashboards, exports and API responses.
Sales works in kanban, accounting in lists, management in dashboards. The same records, with the same permissions, reach each team in its own view; without writing separate reports.
List: each order is one row; columns, filters and sorting are saved with the view.
| Order | Account | Region | Stage | Delivery | Amount (₺) |
|---|
Sample data; company names are illustrative. The product’s 11 view types: list, form, detail, kanban, calendar, gallery, timeline, pivot, chart, dashboard and process diagram.
Standard work is installed from the marketplace as packages: with their tables, views, menu and permission roles. Once installed, it is all yours. What is specific to you is added alongside, on the same platform, under the same rules.
Specific to you
Ready-made modules
Platform
Once the Türkiye Package is installed, the Turkish uniform chart of accounts (TDHP), VAT rates, VAT withholding and income tax withholding tables, social security (SGK) parameters and the public holiday calendar come predefined. The holiday calendar even feeds into formulas.
Incoming e-invoice (e-Fatura) and e-archive (e-Arşiv) — no manual entry
VAT rates, VAT withholding and the income tax withholding matrix are managed on a single screen.
WORKDAYS uses the public holiday calendar; SLA and deadline calculations are based on actual business days.
Personal data export and deletion requests, explicit consent records and role-based field masking under KVKK (Turkish personal data protection law).
Personnel files, SGK details, leave entitlements and balances, timesheet and shift records.
The only difference is where the data lives. You build your configuration in your company’s test copy and promote it to live with conflicts in view; in both models.
MitosOne Cloud
Your own servers (on-premises)
Frequently asked questions
Both. You start with ready-made module packages such as the ERP core, Human Resources, CRM, fleet, manufacturing, accounting and invoicing; then you fit the system to your company by adding your own record types, fields, approval workflows and reports without writing code.
Yes. 19 field types, a formula language with 43 functions, rollup and lookup fields, 11 view types, a visual workflow with 26 nodes, approval stages, row- and field-level permission rules and document templates are all defined in the interface. When needed, it opens up to code through the REST API, signed webhooks and the script step in workflows.
Incoming e-invoices (e-Fatura) and e-archive (e-Arşiv) invoices are imported from UBL-TR files (XML or ZIP); supplier, line item and VAT details are parsed and converted into a purchasing record. The Türkiye Package comes with the Turkish uniform chart of accounts (TDHP), VAT rates, VAT withholding and income tax withholding tables, social security (SGK) parameters and the public holiday calendar. For outgoing submission, we discuss the integrator you use together during the demo meeting.
The choice is yours. In the cloud, each company runs in its own separate database. If you prefer, MitosOne runs in your own data centre, with a signed licence and without needing an internet connection. The same product is used in both models.
Yes. Master data is moved with the bulk import screen; for ongoing integrations there are role-bound API keys, signed outgoing webhooks, incoming webhook receivers that external systems write to as events happen, a tenant-specific OpenAPI definition and REST/SOAP data source connections.
Yes, as records. The Data Collection listener writes packets arriving over TCP, UDP or WebSocket to records; devices that can send JSON over HTTP use the incoming webhook receiver; in “latest value” mode, each tag is kept current in a single record. The process diagram shows these values live and creates an alarm record when a limit is exceeded. There is no PLC/OPC driver and no sending of commands to devices.
The interface and server messages are in Turkish, English and German. You can also define your own record type and field names in multiple languages from the translation screen.
In a 45-minute meeting you won’t sit through a canned ERP tour. Bring one of your processes; let’s build its record type, approval steps and report together on screen. What we build stays in your demo environment.