141–150 of 201 posts
After a U.S. federal contractor told us they loved Plane but couldn't use it due to ITAR requirements, we spent 6 months building a truly air-gapped version. No external connections, no license pings, no telemetry, everything runs in complete isolation. The interesting part: our air-gapped deployment actually runs faster than our SaaS version. Turns out when you eliminate all network latency, things get snappy. This…
[flagged]
I don't think this cynicism is productive. I've had the pleasure of shipping "regular local applications" several times over my career, and to do it you lose a lot of very basic stuff that modern developers take for granted, most importantly software update and debugging telemetry. It's not a small thing to take a SAAS product and bundle it up like this, and most users don't benefit from it, so it's also not a natura…
There is a difference between using irony to rail the grandiloquence with which something is presented and harsh critics of the thing itself or the intention behind producing the thing itself.
Engineering is all about trade-offs, so "nothing is granted without paying some constraint acceptance" is the only fundamental baseline.
the air gapped Jira alternative for regulated industries is a big white board
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 be the next best thing. Air-gapped, fast, and without the Jira bloat.
After a U.S. federal contractor told us they loved Plane but couldn't use it due to ITAR requirements, we spent 6 months building a truly air-gapped version. No external connections, no license pings, no telemetry, everything runs in complete isolation. The interesting part: our air-gapped deployment actually runs faster than our SaaS version. Turns out when you eliminate all network latency, things get snappy. This…
> The interesting part: our air-gapped deployment actually runs faster than our SaaS version. This is the least surprising thing I’ve read all day.
Earlier quoted context omitted.
At this level (govt, 6 figure+ deals) I would at least consider if this problem should have a non-tech solution, and instead have a legal/lawyer solution. In my experience (not US based though) the govt contracts are under compliance programmes as well so the govt agency’s legal/contract mgmt team would probably follow up internally on expiring contracts (ie licences) and require the owning stakeholder to either rene…
Years back a friend of mine's startup failed when USAF pirated their software and the original customer org stopped paying for it. Feds are DMCA immune, so no real recourse.
> Even with our robust self-hosted option, we kept hearing the same feedback from legal and compliance teams: "Private cloud" solutions that still require Virtual Private Network (VPN) tunnels don't meet their stringent requirements. If it has a VPN tunnel to some outside server, you shouldn't really call it "self-hosted*
After a U.S. federal contractor told us they loved Plane but couldn't use it due to ITAR requirements, we spent 6 months building a truly air-gapped version. No external connections, no license pings, no telemetry, everything runs in complete isolation. The interesting part: our air-gapped deployment actually runs faster than our SaaS version. Turns out when you eliminate all network latency, things get snappy. This…
> cloud-only tools like Jira. But Jira is not cloud-only? https://www.atlassian.com/enterprise/data-center
Earlier quoted context omitted.
> Turns out when you eliminate all network latency, things get snappy. Same experience with JIRA. I read all these negative comments here and elsewhere about how slow and clunky JIRA was, and I couldn't relate at all. Then I realized all those who complained was using JIRA Cloud and we were using on-prem, and it all made sense. We've since moved to JIRA Cloud ourselves, and I understand now. We moved and none of the…
> Then I realized all those who complained was using JIRA Cloud and we were using on-prem, and it all made sense. Even Atlassian doesn't use Jira cloud. Btw it's not "JIRA".
Having worked with airdropped software packaging, next step is a multi node setup.
[flagged]
Local apps usually still require installing dependencies from the network, call home for updates, use cloud storage or sharing, and may send telemetry data. Different levels of strictness.
Local application is local, it doesn't deal with network in any way, except if end user goal require to send/receive some external information. So a calculator or a solo game doesn't require network at all, but a chat app or some MMORPG have a legitimate need to access network, but only to communicate with other users.
Telemetry is just an other word for spying. Spyware integrated used to be considered a clear sign of malvolonte project.
Software update can be put as a separated concern.