devanshuarora

3 ms·

1.
by devanshuarora 1y ago
Strictly speaking, air-gapped originally meant physically isolated, no network connections at all. But in practice, the definition has broadened a bit, especially in enterprise and defense settings. Today, it may include closed private netw
2.
by devanshuarora 1y ago
Yes, agreed, if you build with air-gapped in mind from day one, it should just work. In our case, we had to unwind a bunch of assumptions baked into modern SaaS: license checks, analytics, image pulls, update pings… even small things like f
3.
by devanshuarora 1y ago
Yes, absolutely, in a way, we’re just bringing back the old-school model — full package, zero dependencies, runs on your own infra — but with modern tooling and UX.
4.
by devanshuarora 1y ago
Really appreciate that — and totally agree. We’ve been surprised by how many teams in defense, healthcare, and critical infrastructure are still stuck choosing between bloated legacy tools or cloud-only products that don’t check the right b
5.
by devanshuarora 1y ago
To be fair, “not just X—it’s Y” showed up in product marketing way before AI started parroting it. Just saying. :)
6.
by devanshuarora 1y ago
We ran our company on a whiteboard, until we couldn't, so I get it. And honestly it does beat a lot of bloated tools out there. But when you need permissioning, history, workflows, audit logs—and your infra lives in a bunker—we try to
7.
by devanshuarora 1y ago
Totally fair to ask. .so is widely used by software companies as a domain availability solution - think Notion. For regulated environments, the domain doesn’t matter, the architecture does. With air-gapped deployments, Plane doesn’t rely on