[dead]
We built an air-gapped Jira alternative for regulated industries
151–160 of 201 posts
Re: We built an air-gapped Jira alternative for regulated industries
#152After 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.
HN negativity strikes again.
Can't we just read this as "there are 2 wins here: security and performance"?
Which is not surprising, but still a GoodThing(TM) right?
Re: We built an air-gapped Jira alternative for regulated industries
#153They make it seem like a big deal. It’s pretty much how all software used to ship :)
Both those things can be true at the same time: all software used to ship like that, and shipping like that in the current era _is a big deal_.
Spoken as someone who's core differentiator is "self hosted" [0]
Re: We built an air-gapped Jira alternative for regulated industries
#154As a DoD employee, it would be amazing if more companies took this seriously (I'm looking at you health tech bros).
I do take this seriously (see link in my profile), but have to admit that doing so isn't an automatic entry tickets to places like the DoD
Re: We built an air-gapped Jira alternative for regulated industries
#155AGPL continues to be the future of F/OSS
https://vadosware.io/post/the-future-of-free-and-open-source...
Dread it, run from it, AGPL still arrives. Sustainable F/OSS is the most likely to-still-be-active-5-years-from-now kind of F/OSS.
Re: We built an air-gapped Jira alternative for regulated industries
#156Earlier 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…
Just open the network tab and refresh a page in Jira and you will understand. It isn’t too noticeable on a LAN. Stick the internet in there and it is painful. The worst I have seen is self hosted and accessed over Netskope ZTNA. Truly an abomination.
It's not the refresh that screws you. It's the four goddamn dozen asyncrhonous calls it has to make after that refresh has completed to actually fill out the content of the page and let you click through stuff.
I have to load half a dozen tabs of new tickets and then cycle through them triaging and defining fields in a collated manner to make it so my time isn't hugely dominated by waiting.
We used to have on-prem and it was probably about an order of magnitude better, but still nowhere near "XP in a VM accessing a site on localhost" level snappy.
Re: We built an air-gapped Jira alternative for regulated industries
#157Earlier quoted context omitted.
> 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.
HN negativity strikes again. Can't we just read this as "there are 2 wins here: security and performance"? Which is not surprising, but still a GoodThing(TM) right?
Totally agree. Why pick the one negative thing to say instead of saying “this should be done more often” for example. Just aggravating, as a behaviour.
Re: We built an air-gapped Jira alternative for regulated industries
#158Earlier quoted context omitted.
> 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.
If they also realize that having less dependencies makes deployment easier we have gone full circle.
I can't believe how many devs think dependancies are completely cost free...
Re: We built an air-gapped Jira alternative for regulated industries
#159Earlier quoted context omitted.
Having adopted a number of development tools, including Jira and Confluence, it’s amazing people let them sit there chugging away on underpowered machines with hundreds of users quietly complaining about the speed. Throwing some extra CPU cores and memory is so cheap for the quality of life improvement, let alone the productivity gain.
The concurrent (human) user counts at even large companies is probably a couple dozen at most. Usually with these tools, the performance problems magically vanish if you disable all the integrations people have set up. My company is constantly denial of service attacking Jira with Github updates, for example. Edit: typo
I had the experience for a few years of having to run all of the self-hosted development and project management tooling for a government project about a decade back, and the integrations part holds up strong to that experience. The CI system that had been put in place was probably the most sophisticated I've ever seen, but that had some unfortunate side effects like Jenkins jobs being kicked off automatically thousands of times an hour, blasting all of the Atlassian tools with network requests, or Nessus remote logging into and spawning 40,000 simultaneous processes on the servers actually hosting the Atlassian tools.
Self-DOSing is exactly what it was.
Re: We built an air-gapped Jira alternative for regulated industries
#160Big fan of Plane since it's open-core. Doesn't seem to be a lot of options for self-hosted/open-core project management software. The existing ones looks pretty bad, and don't come anywhere close to Jira level functionality.
> don't come anywhere close to Jira level functionality. In my experience that's probably a good thing. I've moved from a company using Phabricator to one using Jira. Phabricator had exactly everything we needed and was very nicely designed and worked really nicely. Jira has everything you need plus loads of other stuff that project managers feel like they need to add. Oh and they'll never clear anything up or fix an…
I've used both as well, I found Phabricator fine for lightweight kanban-style team work tracking, but once we had PMs it was doomed because it would never do what they wanted (they didn't seem to be able to understand that it was not a Scrum system and would never match well).
These days I'd be using Github instead, issues there are also nice and simple. I imagine it would ultimately suffer the same fate in a similar situation though (not that I intend to get there ever again).
The problem with Jira is that it's so customisable and always ends up being customised by "process people" who think all problems can be solved by adding just one more field - but simultaneously it's never possible to customise your bit to work the way you want.