Rootly的封面图片
Rootly

Rootly

软件开发

San Francisco,CA 6,913 位关注者

AI-powered on-call and incident response. Trusted by leading companies like NVIDIA, Squarespace, Canva, Figma, and more.

关于我们

AI-native on-call and incident response. Beautiful, modern, and Slack-native incident management—from your first alert to retrospective. Trusted by 100s of leading companies including NVIDIA, Squarespace, Canva, Grammarly, Elastic, Tripadvisor, and Figma. See why they rate us 5 stars on G2: https://www.g2.com/products/rootly-manage-incidents-on-slack/reviews

网站
https://rootly.com/
所属行业
软件开发
规模
51-200 人
总部
San Francisco,CA
类型
私人持股
领域
Incident Response、Incident Management、SRE、DevOps、SaaS、B2B、Outage Management、Incident Resolution、Site Reliability Engineering和Crisis Response

产品

地点

Rootly员工

动态

  • 查看Rootly的组织主页

    6,913 位关注者

    SRECon’s best after-hours event is happening next week! Be sure to grab a spot before they’re all gone. ??Good drinks ??Great people ??Real conversations on reliability, observability, and scaling ???March 26 | 7-9 PM ??BarreBottle Brewery, Santa Clara Brought to you by Rootly, r/SRE, Sentry, Cortex, and Stanza. RSVP link in the comments.

    • SRECon Arcade Happy Hour
  • 查看Rootly的组织主页

    6,913 位关注者

    “Developers have been going out of business for 20–30 years, but we’re still going strong,” explains Joel E Salas, referring to how AI is another productivity paradigm shift in development — just like Rails was for Ruby in the 00s or Java for portable development in the 90s. Joel is optimistic about the future of development thanks to a platform-based approach to AI: “History shows that when you build more powerful software, people just go up the stack — they go further, they can do more.” Are you at SRECon? Come chat with Sylvain Kalache, Head of Rootly AI Labs, about AI and Reliability! We’re also hosting a Happy Hour tonight with Cortex, Sentry, Stanza, and r/SRE.

  • Rootly转发了

    查看JJ Tang的档案

    Reliability Agents @ Rootly | Forbes U30

    We just launched the Rootly MCP server—production incidents resolved in <1 minute, directly in your IDE (Cursor, etc). Adoption? Absolutely wild. ?? But is the "MCP" hype real or just another AI buzzword? Just ask our customer Brex. “Integrating Rootly directly into editors will accelerate incident investigation and resolution and increase developer efficiency.” - Jarrod R., Principal Engineer at Brex. Developer tooling is entering a new era—and Rootly is setting the pace. Join us this Tuesday at Mintlify's MCP night to see Sylvain Kalache demo the endless unlocked possibilities.

  • 查看Rootly的组织主页

    6,913 位关注者

    Self-driving cars have been a put-off for a while because they can’t kind of work—their driving must be flawless. That’s how Kaspar Von Grünberg explains the level of reliability we should expect from developer tooling. Instead, he critiques the overhyped promises of LLMs claiming to autogenerate your entire infrastructure from a prompt. Agent-first development is coming to platform engineering, just as it is to SRE and every other corner of software engineering. But we need to find the right technology for each step—and know where human supervision is crucial. Want to see the bleeding edge in action? If you’re heading to KubeCon next week, Humanitec will be demo’ing the latest on golden paths at their booth. Definitely worth checking out.

  • 查看Rootly的组织主页

    6,913 位关注者

    You can now connect Rootly to any MCP-compatible AI tool, such as Cursor, Claude, and Copilot. This allows responders to resolve incidents with Rootly’s additional context without leaving their IDE. And that’s not all—the Rootly MCP Server is open source. That’s right, it’s licensed under Apache 2.0 and available on GitHub. Read more about our MCP Server and watch a demo in our blog post (link in comments).

    • 该图片无替代文字
  • Rootly转发了

    查看Sylvain Kalache的档案

    Leading the AI Labs and Developer Relations at Rootly

    Just finished building Rootly MCP server: go from production incident to resolution in under a minute. ?? How it’s done: -Plug it into your IDE (here Cursor) -Import an incident in Cursor’s chat -Cursors investigate the issue based on the metadata -Cursors suggest a fix, you just have to review and save Incident solved, without leaving your IDE. ???? Try it here ?? https://lnkd.in/g4Fh9Cph

  • 查看Rootly的组织主页

    6,913 位关注者

    KubeCon EU ‘25 features 300+ sessions in 22 tracks but none of them are catered to SREs. We’ve gone through the list and selected a few tailored to reliability engineers in four categories: ? Cutting-edge Observability ? Building Reliable AI Systems ? Case Studies of Reliability at Scale ? Deep Dives We highlight talks by Adriana Villela (OTel Maintainer, Dynatrace), Alolita S. (Observability TAG, Apple), Alexa Griffith (Bloomberg), Celalettin ?al?? (Chronosphere) and other exciting speakers. A bunch of Rootly folks will be in London for KubeCon, find us at some of the talks mentioned in our post, our Booth (S780), or one of hour three Happy Hours.

    • The Unofficial SRE Track
  • 查看Rootly的组织主页

    6,913 位关注者

    Rootly and Cortex, both trusted by industry leaders like Grammarly and Tripadvisor, are joining forces to deliver the most comprehensive incident management solution available. By integrating Cortex’s catalog with incident management, responders gain instant access to critical service context, including ownership, dependencies, and up-to-date documentation. Likewise, by incorporating Rootly’s insights into the Cortex Developer Portal, developers gain visibility into incidents affecting their services and can track reliability metrics in their Scorecards.

    • 该图片无替代文字

相似主页

查看职位