Source control and collaboration
GiteaA home for your team’s code.
ForgejoGive collaborative code a community-built home.
GitLabConnect code review with a wider delivery workflow.
OneDevKeep source, issues and builds in one project home.23 applications / Developer platforms
Build a better home for building things.
Code forges, CI servers, deployment tools, database interfaces and application backends all help a development team in different ways. Choose a platform around the workflow it should own and the privileges it will need.
Explore the applications
Choose by the work you want to do.
GiteaA home for your team’s code.ForgejoGive collaborative code a community-built home.GitLabConnect code review with a wider delivery workflow.OneDevKeep source, issues and builds in one project home.Build and deploy
JenkinsAutomate a build you can inspect and repeat.
Woodpecker CIRun a pipeline from your repository's configuration.
CoolifyBring application deployment into your own workspace.
DokployA deployment interface for your application projects.Data and development workspaces
BaserowBuild a shared database people can work in.
PocketBaseStart a compact application with a ready backend.
JupyterLabKeep notebooks, code and results in one workspace.
code-serverBring a development workspace into the browser.Browse this collection
Developer platforms applications
23 applications to explore
Developer toolsAdminer
A compact interface for a database task.
View hosting & requirementsDeveloper toolsBaserow
Build a shared database people can work in.
View hosting & requirements
Developer toolsBuildbot
Describe a build process that fits your project.
View hosting & requirements
Developer toolsCapRover
Give a server a simpler application deployment path.
View hosting & requirements
Developer toolsCloudBeaver
Explore several databases through one browser interface.
View hosting & requirementsDeveloper toolscode-server
Bring a development workspace into the browser.
View hosting & requirementsDeveloper toolsCoolify
Bring application deployment into your own workspace.
View hosting & requirementsDockge
Give Compose stacks a straightforward control panel.
View hosting & requirementsDeveloper toolsDokploy
A deployment interface for your application projects.
View hosting & requirements
Developer toolsDrone
Make repository events start a repeatable build.
View hosting & requirementsDeveloper toolsForgejo
Give collaborative code a community-built home.
View hosting & requirementsDeveloper toolsGitea
A home for your team’s code.
View hosting & requirementsDeveloper toolsGitLab
Connect code review with a wider delivery workflow.
View hosting & requirementsDeveloper toolsJenkins
Automate a build you can inspect and repeat.
View hosting & requirementsDeveloper toolsJupyterLab
Keep notebooks, code and results in one workspace.
View hosting & requirements
Developer toolsNocoDB
Give structured records a familiar table interface.
View hosting & requirementsDeveloper toolsOneDev
Keep source, issues and builds in one project home.
View hosting & requirementspgAdmin
A web workspace for administering PostgreSQL.
View hosting & requirements
Developer toolsphpMyAdmin
Manage MySQL and MariaDB through a browser.
View hosting & requirementsDeveloper toolsPocketBase
Start a compact application with a ready backend.
View hosting & requirements
Developer toolsPortainer
Make container operations easier to see.
View hosting & requirements
Developer toolsRStudio Server
Use an R development environment through your browser.
View hosting & requirementsDeveloper toolsWoodpecker CI
Run a pipeline from your repository's configuration.
View hosting & requirementsChoose with confidence
Which part of the development workflow should this service own?
Take a sample project through the full intended workflow. Use a limited account, intentionally fail a build or connection and restore persistent data after a redeploy. Document any step that still needs a privileged shell.
Define the boundary of the tool
A Git forge stores and reviews code. A build runner executes it. A deployment platform changes infrastructure. Keeping those responsibilities explicit makes access and recovery easier to design.
Separate trusted and untrusted execution
Pull requests, notebooks and build jobs can run code. Plan worker isolation, secrets and resource limits around the level of trust in each workload.
Keep the data after a redeploy
A deployment can replace application code while important data lives elsewhere. Identify databases, uploaded files, repository storage and configuration before choosing a deployment process.
Bring to the hosting conversation: Runtime, build workers, network access, persistent storage and administrative privileges.
How should I compare the developer platforms in this collection?
Code forges, CI servers, deployment tools, database interfaces and application backends all help a development team in different ways. Choose a platform around the workflow it should own and the privileges it will need.
What should I prepare before hosting one of these developer tools applications?
Runtime, build workers, network access, persistent storage and administrative privileges. Each application's profile links to its official project for current requirements and licensing.
What is a useful first test for a developer tools application?
Take a sample project through the full intended workflow. Use a limited account, intentionally fail a build or connection and restore persistent data after a redeploy. Document any step that still needs a privileged shell.