Start here
Templates
Start from a ready-made project. It deploys in one step, and when you want to change the code you copy it to your own GitHub.
The templates
| Template | What it is |
|---|---|
| Spring Boot REST API | A small JSON API with validation and a health check. |
| Spring Boot + PostgreSQL | A notes app with a page and an API. Its tables are made by Flyway, and it comes with a managed database. |
| Spring Boot web app | Server-rendered pages with Thymeleaf, and a form with validation. |
| Static website | One page of HTML and CSS, served by nginx. Nothing is built. |
| WordPress | A blog or website you build in your browser. It comes with a MariaDB database, storage for its files and a cron job. |
| Laravel | A Laravel 13 app on PHP 8.4 with a PostgreSQL database. Migrations run each time it starts. |
| Django | A Django 6 site on Python 3.13 with a PostgreSQL database and a visit counter. Static files are served by WhiteNoise. |
| Next.js | A Next.js 16 app (React, server-rendered) on Node.js 24. |
The Java templates use Spring Boot 4 and Java 21. Each template is a public repository in the oceanlaunch GitHub organisation, so you can read the code before you deploy it.
Deploy one
- Open your workspace and choose Templates in the sidebar.
- Give the app a name and choose Deploy.
- You land on the app's page, where the build log shows progress. A Java or WordPress template's first build takes a few minutes; a site is usually live within a minute.
The app counts towards your plan's apps like any other: see Plans and limits.
Spring Boot + PostgreSQL
Choose A new database (owners and admins, if your plan has a database left) or one of your existing
databases. OceanLaunch connects it to the app before the first deploy, so the app starts with
SPRING_DATASOURCE_URL, _USERNAME and _PASSWORD already set. See
Databases.
WordPress
One click makes everything WordPress needs:
- a MariaDB database (a new one, or one of your MariaDB databases), connected before the first deploy;
- storage at
/data, where WordPress lives (in/data/wordpress): what's left of your plan's storage, up to 5 GB. Uploads, themes, plugins and WordPress's own updates are kept there, so they survive deploys and are backed up every night; - a cron job that runs WordPress's scheduled tasks (
php /data/wordpress/wp-cron.php) every 5 minutes, so scheduled posts and plugin tasks happen even when nobody visits.
The first build takes a few minutes. Then open the app's address and follow WordPress's five-minute setup: site
title, and your admin user and password (choose a strong one: the site is public). Manage it from
/wp-admin. Uploads can be up to 64 MB.
It needs 1 GB of free storage on your plan, a database left (or a MariaDB one to reuse) and an app slot. With a custom domain, add it on the app's Domains tab, then set it as WordPress Address and Site Address under Settings › General in WordPress.
Make it yours
A template app deploys from our repository, so you can't change its code yet. To change it:
- On the app's page, under Make it yours, choose Create your copy on GitHub. GitHub's Use this template page opens; make the copy public or private.
- For a private copy, or to deploy on every push, connect GitHub under Integrations and give OceanLaunch access to the new repository. See Git and deploy on push.
- Back on the app's page, paste your repository's address and choose Switch and deploy.
The app keeps its address, domains, variables and database. From then on it's an ordinary Git app: with the GitHub App connected, every push to the branch deploys a new version.