Zaro
Build agents & apps on top of your context with one prompt.
1.2K followers
Build agents & apps on top of your context with one prompt.
1.2K followers
Zaro is where you can build working software from your scattered work. Everything you know is spread across Gmail, Slack, notes, and tabs that don't talk - Zaro pulls it into one place and lets you build apps from it in minutes: your research, your side projects, your plans, your decisions. Then they keep themselves updated, checking your connections every day so you don't have to. No code. No maintenance. No graveyard of prototypes you started and never finished.
Nas.com
Can Zaro show where each generated app pulled its context from so users can trust what it’s building on?
Postage.to
@nuseir_yassin1 yes that's available on our platform :)
DiffSense
What are the coolest thing you have seen in the wild built with Zaro?
Postage.to
@conduit_design A few that stuck with me:
Someone built a tool that watches their inbox and Slack for anything that looks like a commitment they made ("I'll send that by Friday") and quietly keeps a running list so nothing slips. Simple idea, weirdly life-changing.
Another person wired up a recruiting ops flow that pulls candidate context scattered across threads and docs into one clean view before every interview, so they walk in actually prepared instead of skimming five tabs.
And on the lighter end, the office birthday cake thing is real, someone genuinely built a workflow that automatically orders cakes at the office when's somebody's birthday
DiffSense
@ykaragiannidis That sounds like sweetener products 😅. But its painkiller products that convert users. No pain killer product stories? 🙏 😬
Radiohere
Why this business model "Zaro is priced per organisation" ?
Postage.to
@manikandanux The work Zaro does isn't tied to individual seats, it spans your whole team. The context it runs on lives across the organisation, the apps and agents you build get used by everyone, and the busywork it removes isn't one person's problem, it's the team's. Charging per seat would mean penalising you for adding the very people who benefit, which pushes teams to limit access to save money. That's backwards. We'd rather the whole org use it freely and pay for the value created, not the number of logins.
It also pairs with the credit model: you pay for what Zaro actually does, not for capacity sitting idle. Per-organisation plus credits means the price tracks usage and outcomes rather than headcount.
Jinna.ai
Congrats on the launch! How your project’s approach compares to Claude Cowork and why chose one over another?
Postage.to
@nikitaeverywhere
Claude Cowork is an agent that sits on your desktop and executes tasks for you, point it at your files and apps, describe an outcome, and it does the work end to end. It's brilliant at that. The unit is the task: you ask, it runs, you get a deliverable.
Zaro is aiming at a slightly different layer. We're less about running a task on request and more about the persistent context infrastructure underneath, so the things you build (apps and agents) stand on a shared, living understanding of how your team operates rather than re-deriving context every run. The output isn't just a completed task, it's a durable app or agent your team relies on over time, with the maintenance and stability that requires.
So it's less either/or than it sounds. One is an agent that does the work; we're building the context foundation that persistent apps and agents run on. Honestly a lot of respect for what they've shipped, the whole category moving toward agents doing real work is good for everyone.
congrats on the launch! the real pain is not doing one task manually, it’s doing fifty tiny operational tasks every week.
Postage.to
@olivia_bennett7 This is a great one, and it's high on our wishlist too.
The logic writes itself: if Zaro can already see the work happening across your connected tools, it's in the perfect position to notice "you do this same thing every Monday" and offer to take it off your hands before you even ask.
Proactive instead of waiting for you to describe it.
It's not something we're calling done today, but it's exactly the kind of direction the context layer makes possible, and hearing people actually want it pushes it up the list. Appreciate you flagging it.
Postage.to
@hamza_afzal_butt Love this, and it's very much the direction we're pulling toward. The agent does the work, the dashboard shows you what it's doing and where things stand, two halves of the same thing rather than two separate builds. Taking a messy recurring process and getting both out of one description is a great way to put it.
how Zaro handles permissions when pulling in context from different sources with different visibility rules?
Postage.to
@joshua_cooper2 The principle we build toward is that Zaro should respect the permissions that already exist on your sources rather than flatten them. If you don't have access to something in Slack or a doc, pulling it through Zaro shouldn't become a backdoor to it. Existing visibility rules should carry through, not get washed away the moment context moves into one place.