Why CodeFloe

We tell you where your code lives, what it runs on, and who pays for it.

What's in the box

Pages, hosted by CodeFloe

Enable Pages in your repository settings to publish static files on CodeFloe’s own servers in Germany, with automatic HTTPS and a managed codefloe.page address. Build your site in CI when needed, and use a custom domain. See the Pages documentation.

CI that comes with the account

Crow CI and Forgejo Actions are both available, on shared powerful runners across amd64 and arm64. Both offer a different style to conduct CI/CD - choose the one that suits you most!

Pull Request Preview environments

Every pull request can deploy a live preview over HTTPS, static or containerised, torn down automatically when the pull request closes. For this we use roost, an agnostic-engine that only focuses on this specific task.

Package registries

Container images, npm, Maven, PyPI, Cargo and more, hosted next to the code that produces them. Powered by Forgejo's integrated package registry.

The CodeFloe repository view, showing the file tree and recent commits of the forgejo-codefloe repository — The repository view. Browsing, search, releases, packages and Actions are all included.

A merged CodeFloe pull request, showing its changed files and a line-by-line diff — A pull request diff. Review, discussion and merging work as you would expect from a forge.