GitLab 12.5

I agree. 99 is a lot of money and basic things like epics should not be exclusive to a super expensive edition.

yeah atlassian pricing is way more affordable for small teams. (i.e. 10€/y for everything for a team of ten or below, but they have way higher server costs)

We were able to justify it because the automation would have taken a FTE to impliment. The cost was more than half that for us.

I was at Gitlab Commit London and myself and colleagues raised this with a few Gitlab employees. They seem to be aware their jump from Premium to Ultimate is too big. At their feedback booth I passed on that it would be ideal to pay for what you use.

We use a separate issue tracker so any of that isn't relevant for us, but some of the security would be ideal.

Likewise, we have user accounts for non-development departments (Legal/Compliance/etc) that wouldn't be interested in SAST, for example. If we jumped to Ultimate we would have to pay monthly for those users to access features that never would use.

As I said, they do seem to be aware of this. I wouldn't be surprised if they came up with a different arrangement for Ultimate in the near future.

What kind of established company can’t afford that? For engineers, it represents less then 1% (often less then even .5%) of the fully loaded cost of an FTE.

Yes quite steep if you have enough devs you can pay for in-house gitlab server + admin

GitHub enterprise is much higher and doesn't even include CI/CD. In addition other CI tools I've seen quoted in the $300/seat range.

Gitlab is a steal at a $99 price point compared to other tools.

This.

Here's the story - I'm a dev, I discovered GitLab ~4 years ago, been using it since, we paid for Enterprise plan immediately and are self-hosting it (for internal use).

I work with code. I can't context switch between an app for code, app for CI, app for CD, app for orchestration, app for issues, JIRA, mail, Slack (you get the idea) AND be productive. There's just too much white noise. I want to use a few tools, minimize context switching and do my work.

I'd like to use GitLab alone, focus on business logic I've to code and keep an agile board that my team and I can use.

And here comes GitLab - with a price of $99 per user. It'd cost us $25 000 a month. Just to get an agile board.

So what we did was - we said "screw that, they completely missed the point", I started playing with Gogs: https://gogs.io/ and I decided we can develop a tiny agile board within a few days to suit our needs, integrate it with gogs and ditch GitLab.

I understand there's business around GitLab, I know there are bills to pay and appetites to satisfy but seriously guys - when a dev's bullshit meter goes off (and mine did), you can tell someone made a bad call.

As much as I got used to GitLab's quirks and everything, I'm really now looking forward to replace it - simply due to the fact I felt like they want to rip me off for a meager feature.

It would have been AMAZING if I could get an agile board and have GitLab help me with 60% of the extra-tooling besides my IDE, but nope - someone was too greedy.

I saw many people complaining about this RIDICULOUS pricing, and even more people defend it - that made me give up arguing. From my POV, pricing is ridiculous, GitLab's been marked as yet another company that started off good and started turning evil (hi Google), I'm looking into alternatives - just like I found GitLab when I looked for GitHub alternative.

exactly, the gap is too high, and while being a an absolute gitlab fanboy (been converting all the companies I've been since 2012 and gitlab 5), but here I've no traction to say "let's ditch Jira and switch to ultimate, (we're currently premium), because for 10,20 more dollar, we have both, and yes as other said, suddenly with these features you want to onboard much more people , so you both pay more , and you pay more :)

I agree. Their pricing needs fixed for sure. The lowest paid price isn't bad, and even the middle one, but the top one is way overpriced.

It would also be nice if they introduced some sort of pricing for small orgs, especially for one people shops.

GitLab community advocate chiming in, I just wanted to share a n Epic with plans from our team regarding this issue and future releases. https://gitlab.com/groups/gitlab-org/-/epics/1887

They're a YCombinator company and get the benefit of extra coverage. Stripe is another company with a constant stream of product announcements on HN.

I've wondered if applying to Ycombinator might be valuable simply for the ability to advertise to and recruit engineers.

Helm charts are just templated k8s manifests, you can have it spit out the final manifest and use it manually.

In your deploy step you can just use kubectl and set the user and context with variables you've provided the job.

GitLab product person here - Thanks for the suggestion! I think this issue (scheduled for our 12.6 release coming out next month) should help. https://gitlab.com/gitlab-org/gitlab/issues/27630

:wave: I'm a maintainer of the GitLab helm chart. You can certainly use `helm template` to get the output of our chart, and then make use of `kubectl` without issue. We have several large customers using this pattern, and is expected as an option due Helm 2.x's Tiller component being problematic in compliance regulated industries.

We can certainly work on surfacing this better in our documentation :thumbsup:

I am glad you said it. Right now, the setup is so opinionated that it's limited and suffers from the mile wide and inch deep problem. In particular, they are still behind the Jenkins default setup in terms of standardized xunit output parsing, tracking and visualizing test trends over time - and since they have all the git topology information at their disposal there are amazing possibilities there and its a real shame. They are light years away from large scale project management capabilities of JIRA + plugins and I wish they would improve the core source control + build pipeline experience before tackling that space.

> Tried to use gitlab with all their built-in DevOps feature and found it extremely frustrating to get to a good setup.

All the AutoDevOps stuff is pretty much just some standard build jobs that use Herokuish and Helm, and the inflexibility of them goes hand-in-hand with Gitlab's "breadth over depth" strategy. Hopefully it continues to mature, but for now it's only appropriate for smaller/less complicated applications.

Fortunately it's pretty easy to ignore the AutoDevOps pipeline and still get the benefits of the various integration points that were added to make it work - if a Kubernetes cluster is tied to a project environment then a kubeconfig will be injected into any CI job with the environment set, the same job will automatically get recognized as the deployment job so rollbacks work seamlessly as well, etc. I've done this myself to deploy Mediawiki on Kubernetes, as the default pipeline was not setup for complex multi-component deployments (memcached, mediawiki, apache trafficserver, service endpoints for an external mysql cluster) and it works well.

Sourcegraph CTO here.

> For example, if you pay for GitLab's self-managed "Starter" package, and assuming you spin up your own private Sourcegraph instance [1] to go along with your self-managed GitLab instance, what Sourcegraph features do you get? Will you get code review intelligence, which Sourcegraph charges $29/user/month for?

The GitLab pricing tier has no bearing on Sourcegraph features—it is the Sourcegraph pricing tier that determines what Sourcegraph features are available. $29/user/month is the Sourcegraph Enterprise tier, which includes full code review intelligence (jump-to-def, find-refs, hover tooltips).

Note also that Sourcegraph customers are only charged for active users, so if most of your team doesn't end up using the features provided by Sourcegraph, you aren't charged for them.

> On Sourcegraph's pricing page, it says the open-source edition is missing features like "Single repository definitions and references" and "Cross-repository definitions and references". What does that mean for private GitLab instances?

"Single repository definitions and references" means go-to-def and find-refs work if the code you're trying to jump to is in the same repository. "Cross repository" means you can jump through to code in upstream and downstream dependencies.

If you're running a private GitLab instance, you'll need to deploy a Sourcegraph instance (runnable as either a single Docker image or Kubernetes cluster) and pay for the appropriate license (free if you're under 10 active users and just want single-repository code intelligence, $29/user/month if you're over 10 active users or want cross-repo code intelligence).

Sorry about the confusion here—does that answer your questions?

When on the private, free, you get the features of the unlicensed EE (which behaves as the opensource version).

You can still pay us money if you want, by going with one of the paid tiers, which gives you access to other features and additional CI minutes.

But "free GitLab" is, really, good enough for personal use and small / medium companies when they are starting their digital transformation, or can afford to some manual inefficiencies.

The extra features on the paid tier become more important and urgent as you grow, so by having you already familiar and invested in the product, it becomes more obvious and easier the choice of becoming a paid customer.