Outpost Community Demo

sysadmin here. yes we exist. yes we use forums.

By chmod777 ·

Hey all. I run infrastructure for a mid-size SaaS company. We're spinning up an internal community for our engineering team to replace the graveyard that is our Confluence space.

Nobody reads Confluence. Everyone reads forums if the content is good. That's my hypothesis anyway.

Using Outpost because it has an API (I can automate things), it's embeddable (can put it inside our internal dashboard), and it's cheaper than standing up another Discourse instance that I'll have to maintain.

If anyone else is using Outpost for internal/private communities rather than public-facing ones, I'd love to hear how it's going.

3 replies

Arjun M. ·

We're doing exactly this! Internal engineering community, ~60 people. The threaded discussions work way better than Slack threads for anything longer than 3 messages. And the search is actually usable, unlike Slack where messages disappear into the void.

caffeineOverflow ·

Same boat. Our internal wiki was where good ideas went to die. Moved technical discussions to Outpost and now people actually participate because it feels like a real community, not a documentation graveyard.

The webhook integration is clutch for internal use too — we pipe new topics to a Slack channel so people get notified without having to check another tool.

chmod777 ·

Good to know others are doing this. The Slack notification angle is smart — that's the "meet people where they are" approach. Will set that up.