July 2026

Updates released in July 2026.

Pro apps can store and manage files

July 31, 2026 — Pro apps now have managed file storage

Apps on the Pro tier can now store files in the managed backend. This is the first building block of the Pro managed backend, which will later add secrets, server procedures, an HTTP proxy, persistent logging, public access, and custom domains.

• Store files for your app — upload files from the App Builder and read them from the app at runtime. Useful for configuration, templates, reference data, or generated reports.
• Clear limits — up to 50 files, 5 MB per file, and 50 MB total per app.
• Read-only files — mark files as read-only so the app can read but not overwrite or delete them. Good for configuration and reference data.
• Controlled runtime creation — choose whether the app can create new files at runtime, or only read and overwrite files you uploaded in advance.
• Private by default — files are isolated per app and stored in Operator's managed storage.
• Just ask the App Builder — describe the file the app should read or produce and the Builder wires it up for you.

The feature is available in the new Backend tab in the App Builder, visible only for Pro apps.

Apps built with App Builder can now open and host each other

July 30, 2026 — Apps built with the App Builder can now open and host other apps

Your apps are no longer isolated. An app can now open another app directly, or even host it inside its own UI, so you can build dashboards and hubs that pull together several apps in one place.

• Open another app by name — tell the App Builder "open the Customer 360 app when I click this row" and it wires up the navigation for you.
• Host apps inside other apps — a dashboard app can show another app as a panel, keeping both apps running and connected to the same ERP.net instance.
• Works everywhere — app-to-app navigation and hosting work in the App Builder preview, full-screen mode, and installed PWAs.
• No republishing needed — existing apps can use the new capabilities as soon as you add the behavior in Design mode.

App Builder now uses far fewer credits

July 29, 2026 — Building and editing apps now consumes 2× to 5× fewer AI credits

The App Builder has become significantly more efficient. A set of recent improvements work together to reduce the amount of context the AI has to process on every turn, which means your credits go much further when you iterate on an app.

• Cheaper refinements — small tweaks, style changes, and follow-up requests now cost a fraction of what they used to.
• Faster iterations — the Builder keeps the relevant context in memory and reuses it instead of reloading everything each time.
• More room to experiment — because each edit uses fewer credits, you can try more variations before you notice the impact on your budget.

Existing apps benefit automatically. You do not need to republish or change anything; the next time you open an app in Design mode and ask for a change, you should see the difference.

App Builder now creates installable apps

July 24, 2026 — Every app you build can be installed as its own full-screen app on phones and desktops

Apps built in the App Builder are now real installable apps. Each one gets its own icon and launches in its own window, separate from the main Operator experience.

• Each app is its own install — installing "Color CRM" or "Delivery Analysis" creates a separate app with its own name and icon. Different apps, and even the same app on different ERP.net instances, are treated as separate installs.
• Generated app icons — every app gets a unique icon that belongs to the same Operator visual family: a rounded tile with the app initials and a color generated from the app name.
• Full-screen, no browser chrome — installed apps launch in their own window and behave like native apps on mobile and desktop.
• Install from any share link — open an app someone shared with you, switch to full-screen, and the browser will offer to install it. The install prompt uses the app name and icon, not the Operator ones.

This is available for any app that supports full-screen mode. Users do not need to republish the app; the install option appears automatically.

Manage Instance hub

July 24, 2026 — A single home for everything that belongs to an ERP.net instance

Instance management is now centered around a new Manage Instance hub. Instead of hunting through menus, admins and power users land on one page that shows the health of the instance and offers one-click access to every management area.

• One hub, every management page — open the instance selector in the top bar and choose Manage Instance... to reach the hub. From there you can jump to:
  • Users & Permissions — manage instance users and permission policies.
  • Entity Instructions — teach the AI how your company uses specific ERP.net entities.
  • Organizational Capabilities — connect MCP servers with custom tools and data sources.
  • Credit Management — view and top up the instance's AI credit budget.
  • Spend Statistics — explore where credits are going (see below).
• Live counts on every card — the hub shows the number of instance users, entity instructions, connected MCP servers, and the credits remaining for the instance, so you can see the state at a glance.
• Faster navigation — the hub replaces the older flat menu with the same card pattern used by the Admin and Sales areas, making it easier to discover and switch between tasks.

The hub is visible to instance Power Users and Admins. Ordinary users continue to use the instance without needing to open the management pages.

Spend Statistics

July 24, 2026 — See exactly how AI credits are consumed across your instance

A new Spend Statistics page gives instance admins a clear, month-by-month breakdown of credit consumption. It answers questions like "Which app used the most credits in June?" or "Who is driving the spend on the ERP Advisor agent?"

• Tree view: Instance → Project → User — the list starts with the target instance, expands into projects (apps, sites, or agents), and then into individual users.
• Six months of history — each row shows credit usage for the last six calendar months, including the current month, plus a total across the period.
• Project kind badges — apps, sites, and agents are marked with small badges so you can tell the source of spend at a glance. Built-in agents are shown with their friendly names.
• From the hub — open it from the Manage Instance hub card, which also previews the current month's total spend.

Spend Statistics is available to instance Power Users and Admins.

App Logs

July 23, 2026 — Persistent app event logs — a structured, queryable log for every app

Your apps now have a real logging channel of their own. Alongside browser console output and low-level ERP API calls, apps can emit structured events that are stored on the server, searchable, and available to both you and the App Builder for later analysis.

• Three log streams, one place to view them — open an app's ⋯ menu → Logs to see:
  • ERP API — every Domain API call the app makes through the proxy. Optional and time-boxed: enable it on the app for a defined window when you need to trace a specific issue, and it turns itself off automatically.
  • App events — the new persistent, structured log written by the app itself (see below). Stored for 3 days, searchable, and shared with the App Builder.
  • Console — a live mirror of the app's browser console output. Session-only, never sent to the server; great for real-time debugging while you're using the app.
• Ask the App Builder to log the important things — say things like "log a warning when the discount is over 20%", "log an error if the invoice fails to save, with the customer id", or "log info every time a report is exported". The Builder wires the log calls into the right places for you.
• Structured, not just text — each entry has a level (info / warn / error), a short message, and an optional JSON payload with whatever context matters (ids, amounts, user choices…). You can filter and search by any of it.
• Click any entry for the full detail — long URLs, request/response bodies, arguments and errors open in a copyable, monospace dialog — no more truncated text.
• The App Builder reads the same logs — when you tell the Builder "the export sometimes fails, please investigate", it queries the app's own event log and uses the entries to diagnose the behaviour. You don't have to open the Logs tab yourself unless you want to.
• Safe by default — App events are visible to the app's owner and admins only. Quotas keep noisy apps from filling the log (roughly 1,000 events per day and 60 per minute per app), and entries auto-expire after 3 days.

When to use which log

• Use App events for anything you want to keep, search, or have the AI analyze later — business actions, unusual conditions, failures with context.
• Use ERP API logging when you're specifically troubleshooting how the app talks to ERP.net. Turn it on for a limited window, then let it switch off.
• Use Console for live, in-the-moment debugging while you have the app open. Nothing is persisted.

You don't need to view the logs yourself to benefit from them — just ask the App Builder to look. The tab is there for when you want to see what's happening with your own eyes.