August 2026

Updates released in August 2026.

Meet Digital Entities — agents that keep working on their own

August 17, 2026 — A new kind of agent that remembers, watches, and acts even when you are not around

Digital Entities are the next step up from regular agents. A normal agent waits for your question; a Digital Entity keeps watching, remembers what matters, and steps in when something needs attention.

• They never forget the important stuff — facts, tasks, deadlines, and open issues stay alive across days and weeks, so nothing falls through the cracks.
• They notice what did not happen — a customer reply that never arrived, a delivery that missed its window, a deadline that is quietly approaching.
• They work on their own rhythm — set them to watch a process, a customer, or a list of obligations and they keep checking back.
• They take initiative — when they spot something that needs action, they can warn you, start a task, or record what happened.

Use a Digital Entity to:

• Track contractual deadlines and warn you before they slip.
• Follow up on customers who have not replied in a set number of days.
• Monitor stock levels, orders, or support tickets that need attention.
• Work through a long follow-up list and report progress each morning.

Digital Entities are available as an upgrade for any agent. While active, they use 2 AI credits per day.

Installable apps have a new address

August 15, 2026 — Apps you install now live at app.operator.net

Apps opened full-screen or installed on a phone or desktop now use a shorter, cleaner address at app.operator.net.

• Old links keep working — anything you bookmarked or shared previously is forwarded to the new address automatically.
• One-time reinstall for a clean icon — if you installed an app before this change, uninstall it once from your browser's app menu and install it again from the app's full-screen page. Everything else stays exactly as it was.

More room and better records for Pro apps

August 7, 2026 — Bigger file limits, retirable records, automatic history and a business date

The app backend got a round of upgrades that make it usable for real, growing data sets.

• More room for files — an app can now keep up to 500 stored files and 100 MB in total, instead of 50 files and 50 MB. The 5 MB limit per file stays the same.
• Retire records instead of deleting them — every record now has an Active switch. Lists show only the active ones, a direct lookup still finds a retired record, and retired records can be shown again at any time from the Backend tab.
• Who changed what, and when — every record keeps the moment it was created and last changed, together with the user behind each change. It is filled in automatically, so "added today" and "recently changed" lists are instant.
• A business date per table — a table can now carry one named date that matters to the business: document date, activity date, due date. Date ranges and newest-first lists on it stay fast however large the table grows.
• Steadier record addresses — apps now give each record a permanent address of their own instead of reusing a business code that may later change. Codes stay editable without creating duplicates, while genuinely permanent identifiers are still used as the address where that helps.

Pro apps can call external services safely

August 5, 2026 — Secrets and web requests are now part of the app backend

Pro apps can now talk to other systems — a courier API, a payment provider, a partner platform — without ever holding the credentials.

• Write-only secrets — store API keys, client ids and secrets in the app backend. They can be set and replaced, but never read back: not by you, not by the App Builder, not by the running app.
• One secret, many customers — every secret can have a global value plus a value for a specific ERP.net instance. When the app runs on that instance its own value is used automatically, with the global one as fallback.
• Requests defined once, called by name — the address, headers, body and credentials live in the backend. The app just says which request to run and passes a few parameters, so it can never be redirected elsewhere.
• Logins handled for you — bearer tokens, basic authentication and OAuth2 client credentials are supported, with access tokens fetched, reused and renewed behind the scenes.
• Test before you ship — run any request from the Backend tab and see the response with all credentials hidden.

Both sections live in the Backend tab of Pro apps, next to Files and Tables.

Pro apps can keep their own records

August 3, 2026 — Pro apps now have their own table storage

Apps on the Pro tier can now store structured records of their own — orders, settings, drafts, favourites, checklists — without pushing anything into ERP.net. Just tell the App Builder what the app should remember and it takes care of the rest.

• Records that belong to the app — anything that is not ERP.net business data and not an uploaded document now has a proper home.
• Ask in plain language — "keep a list of the daily requests", "remember my last selection", "save this form so I can finish it later".
• Grouped and searchable — rows can be grouped (by month, category, customer…) and searched by their display name, so lists and reports stay fast even when they grow.
• Per instance or shared — a table can keep separate records for each ERP.net instance, or one shared set for the whole app.
• Read-only tables — mark reference data such as price lists or statuses as read-only so the running app can read it but never change it.
• Browse and edit from the App Builder — the Backend → Tables section lists every table with its rows, a search box, and the full content of any row.
• Generous limits — up to 100 000 rows per table and 200 000 rows per app.

Table storage is available for Pro apps, next to stored files, in the Backend tab.