A self-install would let a school, college or network run the whole platform and GID Studio on its own servers, entirely in its own hands. It is Proposed: the package does not exist yet.
The code is not public yet
The platform’s own code is kept in a private repository today. It still holds material that must not be published: the sources behind the website, faculty proposals, passwords and keys, and the files we use to deploy it. Once that is taken out, the code will be published under the GNU Affero General Public License (AGPL-3.0-or-later), a licence that lets anyone use and change it, as long as anyone who runs a changed version for others shares their changes too. The licence still needs the institute’s IP check. Until then there is nothing to download. Proposed
What you can see today is what the platform is built from: WordPress, LifterLMS, BuddyPress and bbPress, Forgejo, Penpot, Excalidraw and authentik, each under its own open licence. See Open source. Live
What the package would hold
One public repository
With everything in one place.
A compose file
One file that starts all the parts together on a server.
An install guide
, written for an IT team.
Sample data
, so you can try it before your students arrive.
An update path
, so you can move to new versions safely.
Data export and import
, so your data is never locked in.
Proposed
What it would mean for your college
You run it, entirely.
Your college answers for its own teaching, assessment, certificates, fees, users and data.
ODS has no part in your data.
ODS only licenses the code; it does not see or hold anything on your servers.
The code comes “as is”
, without warranty, as open licences give it. Help would come from the community; paid support might be offered for those who want it.
Your own name.
You may run the code, but not present your copy as this school: a self-install uses its own name and says it is not affiliated.
Proposed