3 ms·

We can support GitHub Enterprise with a self-hosted appliance. If you're interested I'd love to talk.

• athenot 9y ago
  That self-hosted appliance would have to undergo a year-long security review process. Basically we'd have to know all the internals, how things are implemented, with which libs, which versions, how it gets updated... For something that really should be a piece of desktop software, that most likely won't fly. I understand your business decision to go for a SaaS model instead of a fixed price, but the added value of the service (vs. a product) doesn't justify it on the user's side.
  • kovek 9y ago
    I wonder, would you be able to check if the self-hosted appliance is making requests to IPs other to the one that hosts your Github Entreprise instance? If you can check for this, you can be more confident that your data is not being sent out to machines you do not control.
    • athenot 9y ago
      That would help build a case for mitigation, but it would still have to undergo the entire scrutiny process.
• lojack 9y ago
  That's going to pretty much be a non-starter for most people. I'd like to use this software and I might be able to get a couple more people at my company interested, but that's not going to be enough to convince anyone to set up an on-premise server to manage the app. Perhaps you would consider a hybrid approach where the actual app connected to the API and set up the required webhooks, which your server could then use to notify the app?