{"version":"1.0","type":"rich","provider_name":"Acast","provider_url":"https://acast.com","height":250,"width":700,"html":"","title":"We Spent a Church’s Yearly AI Budget in One Weekend. Here’s What We Found | Ep 224","thumbnail_width":200,"thumbnail_height":200,"thumbnail_url":"https://open-images.acast.com/shows/5ae332859da29d4b23f0c47e/1791819050522-ffdc21b7-9cbc-42d8-a16c-70acd67d86b7.jpeg?height=200","description":"

AI got very good at surfacing security vulnerabilities fast. In this episode of Rock Cast, Jon, Emily, and Nicole share the story behind Rockʼs recent security releases.

Jon explains how the team built a series of agents to scan Rockʼs code, why Rockʼs flexibility makes every fix a balancing act, and whether Rock will stay open source.


The main takeaway here is that security is a two-way street. The core team is working its hardest to roll out fixes, but they only protect your church once you install them. As a Rock admin, hereʼs your 5 step action plan to make sure your church stays protected and secured:


  1. Install security releases when they land.
  2. Watch for the red banner on your homepage.
  3. Work through the field types guide and move your Lava over.
  4. Keep cleaning up predictable IDs.
  5. Report security issues through Talos.


Visit the show notes to download all the resources talked about in this episode. Don't forget to join the Rock Cast Rocket Chat Channel to see what other churches are saying about this episode.

","author_name":"Spark Development Network"}