Transform your internal engineering docs (Markdowns) into interactive Notebooks with Runme (runme.dev). Store your Notebook sessions, outputs and metadata in Stateful (stateful.com), share on Slack, and build a searchable DevOps knowledge base for your team.
Excited for engineers to be able to explore the power of DevOps Notebooks through Runme and Stateful, it's time for some real innovation around engineering documentation. ππ
Runme was built to restore faith in internal engineering/operational docs - something nihilism had swallowed for decades.
Stateful wraps Runme's powerful DevOps notebooks into an out-of-the-box platform that unlocks critical docs that **actually work** when your team needs them!
Report
Maker
Embracing DevOps culture, I've always found internal engineering documentation to be challenging. Using DevOps Notebooks with Runme and Stateful is a game-changer, making it seamless to create, run, and share live documentation that integrates effortlessly.
This is a fantastic opportunity for engineers to combine Notebooks, DevOps, and dynamic documentation, transforming the way we work! Letβs innovate together with Runme and Stateful. π
Report
Hey @adamchristian
"Stateful" sounds a bit technical, but it basically stores your internal documents and code snippets. The product description explains how it works with "Runme" to make your engineering documents interactive and sharable. Imagine turning your notes into mini-programs your team can use and learn from - a searchable knowledge base for your DevOps crew!
Report
Wow, Adam! This is such a game-changer for engineering docs! π The idea of interactive Notebooks combined with Stateful sounds super powerful. Can't wait to see how this transforms the way teams collaborate and learn. I've been looking for a way to make documentation more engaging, and this seems like the perfect fit! Excited to try it out!
Hi @kyrylosilin, Stateful with Runme at the core is built to handle large-scale docs scenarios, both for your markdown docs and artifacts generated as part of running them.
Stateful relies on proven search/indexing technology to make artifacts searchable and accessible, so it's easy to find the proverbial needle in the haystack. Runme (OSS that actually runs your docs) relies on the colocation of markdown documents in repositories. Both the CLI and the Extension leverage industry best practices (e.g., .gitignore) mechanism to make sure only your relevant docs are being discovered/surfaced.
Happy to answer any detail question if you have something specific on your mind, @kyrylosilin. I'd also encourage you to sign up and give it a whirl yourself at https://platform.stateful.com/.
Thank you!
@mohsen_khani, please let us know what the team thinks!
Report
Congratulations on the launch of Stateful! I'm excited to see where this innovative combination takes the world of DevOps and engineering documentation.
Could you elaborate on how the search functionality works within Stateful? Does it index content in real-time, and how effective is it at handling large volumes of data?
Thanks, @coracat! Yes, the search index currently does record artifacts generated from notebook sessions in near-real-time and makes them searchable. We are confident that we can keep up with teams using these features inside of organizations and continuously invest in keeping the search latency low for practical use cases.
I'd be happy to chat more and interested to hear what "dimensions" of scale you have in mind.
Thanks again for the thoughtful question!
Yep, there's some overlap, @mies@chrismessina. However, Runme, which is at Stateful's core executing the DevOps notebooks, is entirely open source. Runme itself builds on open standards.
Notebooks are great. The more the merrier!
Replies
Stateful
Stateful
Stateful
Stateful
Telebugs
Stateful
Stateful
Stateful
Raycast
Stateful