Internal apps
Ask the agent in your channel for a tracker, a CRM or a dashboard. It builds a small app with its own database, and everyone in the channel can open it, use it and ask for changes.
There is no blank editor. You describe what you need in chat, and the agent builds, fixes and changes the app while you keep talking.
"Track the trucks booked for each dock this week, with a board by status." Start from a tracker, CRM, dashboard or form, or from nothing.
It writes the app, gives it a database and fills it with your data. A CSV import takes up to 10,000 rows.
Changes land in a draft with its own data, so you can test them without touching what the team uses.
The app opens beside the chat and as a live card in the channel. Every version is listed in plain sentences, and reverting keeps your records.
Apps are small on purpose, but they are real software: data, views, logic and access.
Data
Each app has its own SQLite database, backed up continuously with point-in-time restore. Deleted data can be brought back for 30 days.
Logic
Apps run server functions and can wake an agent when something changes, such as a new row or a status that moves.
Access
Keep an app to its channel, open it to the whole company, or publish it to the web. Roles are Viewer, Editor and Builder, and people can ask for access.
Each one started as a message in a channel.
Sales
Target accounts with the people to reach, a warm path to each one, their LinkedIn profiles and the next step.
Operations
Trucks booked per dock and hour, with a board by status. The agent moves bookings when a carrier writes in.
Finance
Open invoices by customer and age, with the reminders sent and the payments promised.
Hiring
Candidates by stage, interview notes and the next step for each, updated by the agent after each call.
Developers can work on the same apps from Claude Code, Codex or a terminal with the laze command, from the first version to publishing, reverting and reading logs.
laze app create dock-planner && laze app push && laze app publishNo. You describe the app in a channel and the agent builds it. People who code can also work on it with the laze command from their own agent.
In the app's own database, hosted by Laze in the EU, with continuous backups and point-in-time restore. You can export it as CSV at any time.
Yes. Every version is listed in a plain sentence, and reverting to one keeps the records you added since. You can also try a revert in draft first.
You choose: only certain people, a channel, the whole company or the public web. Publishing to the web needs an admin's approval.
Yes, through connections in the vault. The app's functions get the access, and the key never reaches the browser.
Yes, if it is published. They sign in with a code sent to their email, and row rules decide which records each one sees.
Each app shows its monthly cost and has a budget, with warnings at 75% and 95% of it.
