We built Backplane so humans and AI agents could work on Valaris projects from a shared project state. Today we're sharing the first public look.
Self-hosted, MCP-native, open source on September 21.
Where does your team keep project state?
https://t.co/8T3w3QZdFs
Backplane is for getting people and AI agents working together.
Backplane Dogfight is for getting absolutely no work done 😄
My cofounder @sssebol and I decided every Valaris product should come with a game or an easter egg. This is Backplane’s ✈️
TGIF. Who’s up for a round?
Our slightly more serious side: https://t.co/XOGjvqFZO6
@Yarilo7brigada I’d keep a small random sample of the rejected posts too. Otherwise you can tell the filter saves time, but not whether it quietly hides something you’d have wanted to read.
@Shpigford Sharing how something works feels different from sharing which customer problem took months to spot. You can be open about the build without publishing your next move.
@rauchg The case I’d want to test: the nightly job updates a memory while an agent is still working from yesterday’s version. Keeping both revisions would make that much easier to untangle.
@steipete The interesting cases will be corrections phrased like casual follow-ups. “One more thing” can mean a new task, or “stop, that assumption is wrong.”
We built Backplane because we needed it at Valaris. That doesn’t mean every team does.
If you already use Linear and coding agents, what coordination work still falls on you?
That’s what my cofounder and I want to understand now that Backplane is open source.