Supported apps
Shiprr deploys source repositories from GitHub and GitLab. The source builder detects common runtimes and frameworks, then prepares your app to run on Shiprr.
How support works#
Supported means Shiprr can send your repository through the source build
pipeline and usually detect the runtime from files like package.json, requirements.txt, go.mod, composer.json, or similar project files.
Detection does not remove normal app configuration. Some projects still need environment variables, a root directory, an install command, a build command, a start command, or a health check path.
Supported runtimes#
The Shiprr source build pipeline currently targets these runtime families:
Framework examples#
These are common frameworks and app types supported through the runtimes above. The list is a practical compatibility guide for source builds, not a separate Shiprr integration for each framework.
JavaScript / TypeScript
- Next.js
- Express
- Hono
- Fastify
- Nest.js
- Remix
- Nuxt
- Astro
- SvelteKit
- Bun
- React
- Vue
- Angular
- Solid
- Sails
- Gatsby
- TanStack Start
Python
- FastAPI
- Flask
- Django
PHP
- Laravel
- Symfony
Ruby
- Rails
Go
- Gin
- Go Fiber
- Beego
Rust
- Axum
- Actix Web
- Rocket
JVM and .NET
- Spring Boot
- Ktor
- ASP.NET Core
- Play
- Luminus
Elixir
- Phoenix
- Phoenix + Distillery
Not supported yet#
- Deploying a prebuilt Docker image directly.
- Deploying with a custom Dockerfile.
- Deploying from a Shiprr CLI.
When detection fails#
If Shiprr cannot build or start the app automatically, set the root directory and commands under App → Settings → Build & Runtime. Start with the same commands you use locally or in CI.
install command: pnpm install
build command: pnpm build
start command: pnpm start