Inngest

Platform for durable workflows and background jobs, including AI flows, with steps that resume after failures.

SSPL-1.0Source-available (not OSI)

Building on it: what may you do?

Short answers based on the licence, for the version in the catalog.

B1 Change the code for internal use in your company Yes, with conditions Usually, for internal use. Check the terms.
B2 Build your own product or service on top and offer it to customers as SaaS No Usually no for a service that competes with the vendor, without an agreement.
B3 Make a closed-source derivative and sell or distribute it No No, not without an agreement with the vendor.
B4 Use the project's name and trademark No No, not without permission. The licence covers the code, not the name or logo.

Keep in mind

There is a licence note for this product (e.g. parts under another licence or version-specific terms): read it and check the licence of the exact version you use.

This is guidance, not legal advice. Check with a lawyer before deciding.

Server Side Public License 1.0 (SSPL-1.0)

Source-available, not OSI. If you offer the software as a service you must publish the source of your whole service stack.

SSPL-1.0. Each version becomes Apache-2.0 three years after it is published.

This is guidance, not legal advice (inte juridisk rådgivning). Check with a lawyer before deciding.

Sign in to see what the licence means for eight use cases – from internal self-hosting to offering the tool as a service.