How it works

Speed without chaos. Autonomy without losing control.

Zaz OS is the foundation your company's apps run on. It handles what every system needs (login, people, permissions, data and AI) so each app only has to handle the process.

1 OS per company2 environments: test and live0 access without permission
01 · Foundation

Every company gets its own OS. Nothing is shared.

When your company joins, we spin up an OS that is yours alone: server, database and files kept apart from every other customer, hosted in Brazil. Everyone runs the same version of the OS. One company's data never touches another's.

testWhere you buildCreate and adjust apps with test data. Break things freely.
liveWhere the team worksOnly gets what has already been tested.
gatekeeperNobody talks to the database directlyScreens, automations and AI ask the OS for everything, and it checks who is asking.
02 · Apps

Each app is a complete package. It goes in whole and comes out whole.

Expenses, time off, onboarding: each app carries everything it needs inside the package. Installing means dropping the package into the OS. Uninstalling means taking it out, with nothing left behind. Zaz keeps the ready-made apps updated; the ones you build are yours, and no update ever touches them.

AI actionsWhat your AI can ask the app for, like "who is on vacation?".
ScreensWhat the team sees, with your company's look.
RulesThe process's calculations, validations and approvals.
AutomationsReminders, notifications and integrations that run on their own.
DataThe app's tables, kept apart from other apps' tables.
PermissionsWho sees and who does what, defined by the app itself.
03 · Governance

Explicit permission or nothing. Guests start at zero.

Nobody sees anything by default. Every access is a rule someone granted, app by app, and the rule applies the same way to people, automations and AI.

rolesFive, in every appAdmin, builder, manager, member and guest. The app says what each one can do.
across appsOnly with authorizationAn app only reads another app's data if someone allowed it.
historyWho, what, whenEverything is logged, including what was denied.
04 · Intelligence

Use the AI you already have. It runs the apps with your permissions.

Connect Claude, ChatGPT or Cursor to your OS by signing in with your company account. From then on, the AI uses the actions each app offers. It only sees the apps you allowed and only does what you could do yourself.

connectionOne login, nothing to installYou pick which apps the AI sees. The admin can switch it off for the whole company.
writingActing only with your go-aheadLooking things up is on by default. Approving, submitting or editing only if you allow it, and the AI asks you to confirm.
studioNew apps come with actionsWhen the Studio builds an app, it builds the AI actions along with it.
See the AI at work ↓
05 · Publishing

Test first, publish after. No surprises.

Everything starts in the test environment. When it's ready, you publish, and the OS checks the whole app before releasing it to the team. If something fails, nothing changes for the people using it.

versionEvery publish becomes a versionIf needed, roll back to the previous one in one click.
liveWithout interrupting anyoneThe switch happens while the team keeps working.
In practice

The AI works inside the rules. It builds in the Studio and operates through your AI.

On the left, the Studio building an app and its actions. On the right, Claude using those actions. Both go through the same gatekeeper you do: if you can't see salaries, neither can the AI.

Studiotest
create_entitiesvehicles · fines · maintenance✓
generate_screenslist · form · approval✓
set_permissionsfinance approves · manager submits✓
create_mcp_toolsAI actions: pending_fines · schedule_service✓
✓ fleet app ready in the test environment
Claudeconnected to your os
who_is_awaytime off app · lookup✓
Next week, 3 people on your team are out: Bruno (vacation), Carla and Diego (time off).source: time off app · ana.souza's access
readpayroll/salariesdenied
I can't see salaries with your access. The request was logged.ana is a manager · no access to payroll
✓ 2 requests · 1 denied · logged at 2:05 pm
Under the hood

For those who want to look under the hood.

Databasededicated PostgreSQL per environment · hosted in Brazil
Data gatekeeperevery read and write goes through the OS · no screen touches the database
MCP and actionsClaude, ChatGPT, Cursor · company login · lookups allowed, writes with permission
Automations and notificationsOS bell, Slack, WhatsApp or email · one app triggers another
AI inside the appsreads PDFs and images · transcribes audio · searches the web
IntegrationsSlack, LinkedIn, Stark Bank and more · scheduled sync · keys in a vault
APIsone for the signed-in team
one for other systems, with a key
one for what you publish
Hostingdedicated server per environment · updates without downtime
Login, files and historysingle sign-on · files per app · every action logged
Scope

Is it for you? Depends on the problem.

Solves

  • Manual rework between systems that don't talk to each other
  • Spreadsheets that became the real system
  • Approvals with no trail, over email or WhatsApp
  • Zero real-time visibility into the operation
  • Depending on IT, or a vendor, to change a field
  • Internal processes nobody sells software for

Not for

  • The product you sell to your customers
  • Throwaway prototypes and validation MVPs
  • Processes that fit in a form and an email
  • Replacing tax ERP or payroll
Start this week

Operational chaos, finally organized.

A live demo in 20 minutes, around your operation's processes.

YOUR OPERATIONTODAY