#487 Data Sovereignty

This week, we hosted a training day for a new, large self-hosted client in the defense sector.

Reviewing the data from this past quarter has been remarkable. At no point in our company’s decade-long history have we seen so many inbound requests for private- and self-managed instances of our software.

Some customers are in regulated industries (defense, healthcare, finance, etc.). But many should be able and want to use our SaaS, but they are opting for more privacy instead.

It’s likely not a coincidence that we’re seeing more requests for how to integrate applications and AI-based agents against our API. Customers are willing to pay a premium in order to have sovereignty over sensitive data.

The number of meetings ran this week rebounded, suggest that last week’s interruption to team’s collaboration habits was likely Easter-holiday related.

…gave a training to a large, new defense customer. We’re excited to be bringing Parabol to one of our most secure and interesting customers yet. Over 140 team leads attended this first training session. Parabol Pages replacing Data Center Confluence was a big part of the draw…

…re-launched Parabol at Platform One. After a brief interruption in service, Parabol is once again live at DoD Platform One.

…shipped v13.10.3 into production. We fixed a number of bugs, race conditions, and a minor memory leak.

…continue working on updates to getting Parabol’s API ready for general release.