One AI-powered workspace where your projects, conversations, reviews, and creative work stay connected. Every tool switch interrupts creative thinking, scatters context, and adds unnecessary cognitive load. RunEvr is built to keep your entire creative workflow in one place, helping teams stay focused, collaborate naturally, and create without losing momentum.
Hey Product Hunt 🐱
We're excited to finally introduce RunEvr.
RunEvr was born inside our animation studio. Every project involved artists, producers, clients, and partners, but the work itself was scattered across chats, task managers, cloud storage, whiteboards, and endless browser tabs. We weren't losing files - we were losing context.
So instead of adding another tool to the stack, we built the environment we wished we had: one place where projects, conversations, reviews, files, collaborative boards, and AI agents work together in the same context.
We used RunEvr internally for real production before sharing it publicly. It became the space where our team planned projects, reviewed creative work, discussed ideas, and kept everything connected without constantly switching between apps.
Beyond productivity, we wanted collaboration to feel more human. We love storytelling, creativity, and building things together, so we designed RunEvr to be a workspace that's enjoyable to use - not just another dashboard.
In RunEvr, AI agents can become part of the team - taking roles like project coordinators, managers, or creative contributors. They work alongside people as equal members of the project, helping teams organize, create, and move ideas forward while keeping humans at the center of the creative process.
Whether you're building a product, producing creative work, running a community, learning with others, or managing personal projects, our goal is simple: keep everything connected so your ideas can keep moving.
We'd love to hear your thoughts:
Where do you feel collaboration breaks down the most today?
We'll be here all day to answer questions and would genuinely appreciate your feedback. 🚀
The context-preservation problem feels especially real for creative teams because feedback often arrives in different formats and at different moments. When a project moves from rough idea to approved asset, how do you keep the original brief, review decisions, and current version connected so an AI agent can help without treating an old comment as still authoritative?
@wesc Great question!
This is actually one of the hardest parts of creative workflows - not just storing information, but understanding what is still relevant.
In RunEvr, we keep the project context connected: the original brief, discussions, feedback, versions, and decisions all live around the same project. Version history helps separate what was an earlier direction from what became the approved outcome.
For AI agents, the goal isn’t to treat every comment as truth - it’s to understand the evolution of the project: what was suggested, what was changed, and what the current state is.
Congrats 👏@adana on hitting product hunt today. how do you handle versioning history when team members iterate on media assets inside the board?
@priya_kushwaha1 Priya, thanks for the question! 👋
Versioning is decoupled from the Board - it's just a canvas that references files, not a version history itself.
New versions get created either when a task/stage is finalized (each retake/approval bundles into a version), or when someone manually uploads a new overall version at the room level (e.g. "Episode 3 complete").
Iterating on the Board itself doesn't fork history - only finalize/approve or an explicit new upload does.
@adana Interesting approach thanks for explaining it!
Congratulation @adana on the launch! The all-in-one bet usually breaks when one bundled tool loses to the specialist it replaces. Which capability did you decide had to be best-in-class, and which is okay being good-enough?
@aidan_codefox Thanks Aidan, appreciate you asking this!
We're not chasing all-in-one to beat specialists - the bet is context preservation. Our Forum and Drive aren't trying to out-Slack Slack or out-Dropbox Dropbox, they exist so your people and assets live in one room instead of scattered across dedicated tools. The one area we're pushing hardest to be best-in-class: the real-time Board - creatives reviewing media together live, no screen sharing, actual data sharing.
Congratulations on the launch Adana and team - this actually resonates with me
We went through like 3 different project tools trying to find one that didn't feel like adding another context switch and it was frustrating..
Also genuinely curious how real-time collab feels when you've got multiple people on the same asset
@better_shaya Thanks so much Shaya, glad that resonates - that context-switch fatigue is exactly why we built RunEvr this way.
On real-time collab: multiple people can be on the same asset in the Board at once, live cursors, comments, and reactions land in real time, no screen sharing needed - it feels more like being in the same room than passing a file back and forth.
Would love to have you try it and hear what you think.
creative work is messy in a way regular pm tools struggle with - feedback like 'make it pop more' or 'not quite the right vibe' doesn't map to a clean task/status update. how does the agentic layer here handle that kind of subjective revision request versus a normal checklist item, or is it still mostly structured around trackable tasks under the hood?
@omri_ben_shoham1 Really sharp question - this is exactly the gap we obsess over. You're right: "make it pop more" dies the second you flatten it into a ticket.
So we don't. That feedback lives right where the work is - a comment or voice note pinned to the exact frame, so the vibe and nuance stay intact instead of getting squeezed into a status field. There is a light structure underneath (task → take → review → new take), but it's just there to track where things stand - whose turn, needs another pass - not to define what the feedback means. When an agent picks up a revision, it's working from the real note on the real asset, then hands a new take back for review. Human-in-the-loop, not a checkbox.
So yeah - there's a skeleton under the hood, but it's deliberately thin. It keeps the messy back-and-forth moving, not sanitized.
Honestly though, you've given us a really good angle to keep chewing on - it's exactly the kind of thing we want to keep thinking deeper about. Thank you for that. 🙏
"Agentic project management" is in the product name but the listing doesn't describe what the agent actually does. Is there an AI layer that's doing something like auto-updating task status based on conversation activity, summarizing review feedback into action items, or suggesting next steps, or is "agentic" more of a positioning word rather than a description of how the product actually behaves?
@ansari_adin Fair challenge Ansari— and honestly, "agentic" here is more literal than the examples you gave.
It's not an invisible AI quietly flipping task statuses in the background. Our agents are actual teammates you assign work to — they join a room, take a task, do it, and hand it back through the same review loop a human would. You're not babysitting an assistant; you're delegating to a worker.
Aurora is the clearest example — a manager you just talk to. Tell her "set up shots SH001–SH010 and split them across the team," and she'll batch-create all ten tasks, round-robin them to your performers, each with its own description and deadline. She can spin up rooms and stages, invite members, reorganize and reprioritize tasks, set up review chains, and pull deliverables back into the conversation. Two things keep it safe: she only ever acts with your permissions (never more than you could do yourself), and every change she proposes shows up as a preview you approve or reject before anything actually happens.
Then there's Iris, a scriptwriter — give her a brief, she drafts and revises. Lan, a concept artist who creates and iterates from your feedback. Plus quieter helpers doing translation and transcription, so notes and scripts cross languages without leaving the room.
So "agentic" isn't a buzzword for us — it's the whole point: AI teammates that actually do the work, accountable to the same review cycle as everyone else. Some are live today, more landing right after launch. Early, yes — but real. 🙂
@rafik_mkhitaryan The Aurora example is specific enough to actually illustrate what "agentic" means here, batch task creation with round-robin assignment from plain English is a concrete capability rather than a positioning claim.