Directus – real-time REST and GraphQL API of any SQL database

Re:Directus – real-time REST and GraphQL API of any SQL data... by rijkvanzanten on Tuesday February 25, 2025 @09:13AM (#43172081)

Totally! I'm also not saying — at least didn't intent to — that we're doing the exact same approach as Sentry here :) I meant that as "Directus is like Sentry in the sense that it moved away from FOSS as it ran into the OSI rules around no-license-discrimination-against-groups-or-use-case.

Part of the trickiness for Directus specifically is that it's intended to be self-hosted first software. Going all-in on the SaaS as the moneymaker means divesting in self-hosted and focussing on differentiators for the SaaS offering to make up for the loss in funding of folks who self-host.

> I do want to reiterate that a specific "total revenue"/"total funding" figure != "making a lot of money" and I don't think your license captures this nuance at all, today.

Agreed! It's been the best I've been able to come up with, but it isn't perfect. Out of curiosity (not snark), what metrics would you have used as a more generic measurement of (large) company?

[ Parent | on HN ]

Re:Directus – real-time REST and GraphQL API of any SQL data... by lol768 on Sunday March 02, 2025 @12:16PM (#43232604)

EBITDA? I'm not going to claim it's perfect (and if the company is struggling and paying back loans it's going to ignore the interest charges), but the idea behind it AIUI is that you strip out some of the, perhaps, "creative accounting" (that is mostly there to reduce a corporation tax bill) and deductions and focus on earnings/cost-of-sales. Which, should, in theory relate to how much a company can afford to pay for ancillary services.

In the industry I work in, between 96%-97%+ of revenue is the cost of the sale and is immediately handed over. Many purchases don't make a profit at all (fixed costs, commission doesn't cover them so it's loss-making - but you need to be able to offer them anyway).

[ Parent | on HN ]