The fastest knowledge base for software teams, Outcrop.
A lot of teams enjoy using Linear for product management but still have to use Notion and Confluence for knowledge management. I’ve built Outcrop from the ground up to be fast with much more reliable search and realtime collaboration.
Hundreds of teams from startups and major companies have signed up for early access and many have made early commitments to support the development of Outcrop.
If your team would be interested, I’d like to hear from you!
Working on https://outcrop.app, a knowledge base for software teams with instant search, realtime collaboration, and LLM-driven workflows. It's built using Rust and friends. I'm looking for more early testers! :)
Hi HN! For the last 8 months we've been working on building Outcrop, a modern knowledge base for software teams. We see it as the Linear equivalent to Atlassian Confluence.
Working with teams at companies of every size, we've experienced first-hand the shortfalls of current knowledge base tools (Confluence, Notion, ...). They're too slow, unintuitive, unfocused, cluttered... For a tool that we rely on everyday, our expectations were much higher. So we decided to build the tool we always wanted.
We spent quite a lot of time figuring out the details. We avoided many technologies that would've otherwise made this task quite easy, but would've resulted in a bloated and slow experience. We built a lot of custom, realtime, integrated services, using Rust, that includes our realtime collaboration engine, authorisation system, and search engine. Getting these foundational blocks right has been really important, as they'll enable us to build features that none of the other tools have ever attempted.
We're quickly approaching our first release and we're looking for early users who'd like to try out the product. We're also looking for early sponsors to help fund and shape the development of Outcrop. We've got quite a lot planned out for the future, and we can't wait to share it with the world!
Feel free to also contact me through imed at outcrop.app.
I've been working on Outcrop full-time for a few months now, since I left my job at Stripe. I think knowledge base systems are some of the most important components for successful companies. Current tools are too slow and too messy. Many companies end up developing a custom internal wiki to supplement their Confluence one.
Outcrop is powered by custom search, collaboration, and authorisation engines. Everything is indexed, including comments. Search and navigation are instant. I have a long list of itches I want to scratch with this product. I'm doing a round of private previews to collect feedback, if you're interested, please sign up, I'd love to talk you!
Here's what I do: I start reading from the last paragraph.
I can barely get myself to read anything long, even exams! Somehow, starting from the last paragraph, and sometimes even the last sentence, and going back, makes me actually read the text. This also worked with research papers (conclusion -> 1st paragraph). Maybe give it a try?
I do this too. There’s something about reading things backwards that more actively engages and focuses my mind.
It’s partly because seeing the conclusions first triggers a “why”, that I then have to go back and discover in the previous explanations. Most research papers put the final conclusions in the abstract, but each subsequent section and paragraph also ends with intermediate conclusions. Read those first, then go backwards to find out why.
It’s also partly because it forces my mind to actively rearrange the knowledge coming into it, rather than having it all neatly pre-arranged by the author.
Maybe other things too, but for whatever reason it helps me be an active, rather than passive, reader.
That's actually not possible. We provide 2 keys, a private one and a public one. Lambdas could only be edited using the private key. The public key, which you're supposed to be using in production, allows you to only execute the (already deployed) function.
Was this explanation good? I will add it to the landing page in case someone had the same question.
