Glyphi TeamsTeams

Fund what your team needs.Keep the rest MIT.

Sponsorship pays for the parts of the Teams edition a single company would otherwise build alone. The result goes into the public repository, under the same MIT licence, for everyone.

Ways to help

Three shapes of sponsorship

Feature sponsorship

Fund a specific piece of the manager window — SSO with your provider, a billing export, an on-premise installer — and the work ships in the public repository.

Sponsor a feature

Engineering time

A block of days from the maintainer, spent on your fork: branding, an internal installer, a migration from your current tracker.

Book engineering time

Project support

No deliverable attached: you keep the MIT edition maintained and the self-hosting guide current. Acknowledged in the repository.

Support the project

What it changes

Where the money goes

Maintaining three platforms, the Supabase backend and the self-hosting guide is the cost of keeping the Teams edition usable without seat metering. Sponsorship covers that work and buys the sponsored team a direct line on what gets built next.

Every sponsored feature lands in the public repository. Nothing is held back as a private build.