Display
Create docs and apps with any agent, in one workspace
517 followers
Create docs and apps with any agent, in one workspace
517 followers
Create and collaborate on docs, prototypes and apps with your team. Store the files your agents make, organise knowledge work in spaces and folders, and turn it all into your internal knowledge base. Work with any agent and any plan, at a flat price.
This is the 2nd launch from Display. View more
Display 1.0
Launched this week
Create and collaborate on docs, prototypes and apps with your team. Store the files your agents make, organise knowledge work in Spaces and Folders, and turn it all into your internal knowledge base. Work with any agent and any plan, at a flat price.
Free Options
Launch Team / Built With
CloudflareDeploy serverless functions globally in seconds
Promoted
Hey, Product Hunters!
I’m Ott, the co-founder of Display.
Today we’re launching Display 1.0.
Why we started Display
As developers and founders, we were using agents to create beautiful and useful HTML docs. We kept on hitting the same wall:
How to collaborate, edit and comment on docs with our teams?
How to organise the knowledge we created, so that it can be accessible and reviewable to our team and clients?
How to turn all the knowledge into an internal knowledge base for all agents for all future work?
What we wanted to build from the start
The collaboration workspace for your agents and your team, open to any agent.
Before we could do that, we first had to build a simple way to create and publish agent-native HTML and Markdown docs, with simple access controls. Any agent could create and collaborate on the docs, humans could edit.
Today, we’re finally ready open up the next phase of our vision.
Here’s what you can do with Display today
Create and collaborate on docs, prototypes, apps with your team
Store and access files made by your agent
Organise knowledge work in Spaces and Folders
Turn everything you create into your internal Knowledge Base
Work with any agent and any plan
Safeguard your work with access controls – give each team its own Space and decide who can see what
Invite clients and partners to any folder or document, like in Google Drive
Full access for your whole team at a flat price
Here’s what’s next
We have internal apps and data connectors working in private beta, available shortly to everyone.
We’re here today and the whole week to respond to your questions and suggestions.
Let’s build the workspace for your team and agents together.
- Ott, Carl & the Display team
love this! do you have an enterprise plan also?
curious about version history when the agent updates stuff - i can see this running in the background of vertical ai tools that solve a bigger task, where the user explicitly does not use display.dev but still gets the sharing, commenting and versions. is that something you’d support, like an api or white label?
@lotarete we do, yes - anything custom storage-wise, SAML and major orgs are part of our Enterprise package.
Version control is part of all paid plans and it keeps every version of the doc or app available, and you can restore previous versions at any time.
On the topic of using it in the background, it's certainly possible and it's how some companies use it today. You can scope dedicated API keys and use them with custom instructions over CLI or MCP.
I'm on a personal Max plan, but my company uses the team plan. Can we still collaborate?
@andry_pedak great question - I assume you're talking about the Claude plans. It's a common problem for why teams eventually choose Display, since you can collaborate across different plans whereas in Claude you can only work inside a single Teams or Enterprise plan. On top of that, you can also use different agent providers, you're never locked in - e.g. Codex and Claude users can work on the same app or doc.
What's the most underrated use case you have for the tool internally that people don't talk about?
@kaspar_tiri building and iterating on design prototypes for every feature in the product. We build clickable, scenario and user-segment based prototypes for everything, and once they're good enough, it's a lot easier to ship it to production.
Incredible, one thing I'm curious about tho. As agents create more and more documents how do you prevent the knowledge base from becoming a mess of outdated or duplicate information?
@ralf_ellervee Hi Ralf! Great question, no easy answers here – the way we're approaching it now is providing agents clear guidance on what's the source of truth and what's not.
One of the features we're considering is verification markers, which would provide agents and colleagues with clear information when and by whom the doc was actually reviewed and marked relevant.
We're certainly open to ideas and feedback here!
@ottilves good thinking
@ralf_ellervee btw do you have thoughts/ideas on this topic or have you had to address it somehow?
Great product! Was wondering if you have any experience how to best sell/describe this to a non-technical team lead? Would love to send this to some of them? Thanks!
@auklik I'd say it's an agent-native Notion or Google Drive - it's an internal knowledge base of everything your team and your agents make, in any format, doc or app.
Using it every day. Our use case is sharing artifacts where the audience does not match the Claude plan team structure. Decoupling who's in your Claude team from who sees your content is a thing none of the AI labs are incentivised to solve, so that's a smart idea!
@ivokund great feedback and use case, Ivo!