Licensing, answered.

The Apache License 2.0, an OSI-approved open source license. Both public repositories carry it, and the full text is on GitHub. It includes an explicit patent grant, so you get a patent license along with the code.

Earlier releases shipped under it and stay under it. Everything from this release onward is Apache 2.0: the reserved uses, the separate agreements, and the enterprise license are gone. Running the latest release is the simple path.

It is the Android model: open code under a permissive license, a protected trademark, and optional services on top. It makes "open source" literally true and means consultancies, MSPs, and cloud providers can build on Grengin without a licensing conversation.

No. The software and cloud marketplace images are free for everyone, at any size, for any use. You pay your cloud and AI providers directly.

Yes, you can use it commercially, and company size or revenue does not matter. There are no thresholds and no commercial license. A two-person startup and a Fortune 500 run the same free software on the same terms.

Yes, and you need no agreement with us to do it. The one thing you cannot do is market that service under the Grengin name or logo without a written agreement with Perter. Describing it accurately, for example as "a managed service built on Grengin", is fine.

Yes, freely. If you distribute a fork, keep the LICENSE and NOTICE files, say what you changed, and give it its own name and logo. Saying it is "based on Grengin" is welcome.

Yes, including paid and proprietary products. Ship the LICENSE and NOTICE files with the code.

The "Grengin" name and logo. They identify official builds from Perter. Forks, derived distributions, and third-party hosted services use their own branding. Truthful references such as "built on Grengin" and "compatible with Grengin" never need permission. Read the full trademark policy.

Grengin is built in-house at Perter, and the repositories are public so you can read, run, audit, and fork the code. Issues and small pull requests are welcome. There is nothing to sign: Section 5 of the license says that anything you submit for inclusion comes in under the project's own license.

Include the LICENSE file, include the NOTICE file, keep the copyright notices, and say which files you changed. That is the whole list; Section 4 of the license has the exact wording. Trademark questions go to licensing@grengin.com.

The software should be free and genuinely open for the people who use it. Perter funds the work through the things only Perter can offer: the brand, official builds, support, and managed offerings, not by restricting what you can do with the code.

The core stays free, complete, and open source. Released code stays released: Apache 2.0 cannot be revoked for versions already published, so there is no rug-pull to worry about. Source stays public and the roadmap stays transparent.