TMFrom repo
to running app.
Your app, Postgres, authentication, and files.
One workspace. From the first commit to what’s next.
Start free. No credit card. No expiration date.
TM
Search projects, or type a command ⌘ K Connect agent to FortlyDocsJJamie
Your live app stays available while this update builds.
Deployments
Choose your code. Follow its first release here.
Connect your repository
Pick the repository you want to deploy.
- 1 Source
- 2 Configure
- 3 Deploy
Ready to deploy
Review the essentials. Advanced settings are optional.
- 1 Source
- 2 Configure
- 3 Deploy
Environment variables Optional
No variables are required for this example’s first release. We’ll add a publishable key in the Update chapter.
Deployments
Build, publish, and follow every release in one place.
Your deployment is live
launchboard-studio.fortly.com241a7c8First release
- Source receivedstudio/launchboard
- 2Build completeBuild finished
- 3PublishedYour application is available
Build outputComplete
No matching output. Try another search.
- Source
- GitHub · studio/launchboard
- Branch
- main
- Commit
- 241a7c8
- Runtime
- Node.js · Next.js
Database
Explore your data, manage its structure, and control API access.
In the console, use Add relationship or drag between columns to review a foreign key before creating it.
| id int8 | name text | status text |
|---|
Public access to projects
Allow Public visitors to read these records.
These are example permissions for this local demo.
Select Send request to inspect the example response.
Deployments
Values, releases, and the application they serve.
"use client";
export async function loadProjects() {
const res = await fetch('/_data/projects', {
headers: { Authorization:
'Bearer ' + process.env.NEXT_PUBLIC_FORTLY_KEY }
});
if (!res.ok) throw new Error('Request failed');
return res.json();
}
- Name
NEXT_PUBLIC_FORTLY_KEY- Value
-
cvp_example_publishable_key - Scope
- Build only
A publishable key belongs in frontend code. Its saved role permissions control access.
Launchboard
Your projects. Your next move.
Observability
Understand traffic, inspect application output, and follow project activity.
Sample traffic · focus the chart and use arrow keys to inspect.
INFO Application started host: 0.0.0.0 port: 8080
ONE PROJECT. EVERYTHING CONNECTED.
The pieces belong together.
Your application and the essentials around it, in one place.
01 / START WITH WHAT YOU HAVE
Bring the code.
Keep the momentum.
Connect a GitHub repository and deploy on push. Upload a project archive. Or find a ready-made app to make your own.
Your first deploy, step by step
02 / GO BEYOND THE DEPLOY
Your data shouldn’t be
a different project.
Browse records, explore relationships, and set API
permissions.
Work with your database without leaving your application behind.
| id int8 | name text | status text | owner_id uuid | created_at timestamptz |
|---|---|---|---|---|
| 1 | Launch website | Shipped | a81e…92bd | 2026-10-12 |
| 2 | Customer portal | Building | a81e…92bd | 2026-10-14 |
| 3 | The next idea | Planned | f2a4…c18e | 2026-10-17 |
projects
id int8name textowner_id uuidtasks
project_id → projects.idtitle textmembers
project_id → projects.iduser_id uuidACCESS, WITH INTENT
Choose the role.
Review the permissions.
Open the tables and operations your app needs. Connect a trusted identity provider for app-user sessions and row policies.
Read about API access/_data/projects?select=id,name
[
{ "id": 1, "name": "Launch website" },
{ "id": 2, "name": "Customer portal" }
]03 / STAY CLOSE TO WHAT’S RUNNING
Know what’s live.
And what to do next.
Follow traffic, inspect logs, and keep a way back.
The next action stays close to the information you need.
A clearer view of your traffic.
SAMPLE DATAExplore sample traffic. Every point has a detail.
Hover, tap, or use the arrow keys to inspect.
Metrics, logs, and activityShip with a way back.
Explore both outcomes. A failed build keeps the working release live.
Your previous version stays in release history.
main · 8b42c71Current release
Rollback restores the application release. Database changes, files, and environment values stay as they are.
Explore the release workflowTap a project or the Fortly hub to wake an idea.
Some ideas need time.
Give them a place.
No traffic? Your project rests. A visitor arrives? It wakes.
Your
URL, database, and files stay right where you left them.
-
01
Quiet doesn’t mean gone.
A project at rest keeps its place on the internet.
-
02
The next request is its cue.
A visitor arrives. Your application wakes.
-
03
Pick up where you left off.
The same URL. The same data. The same possibility.
05 / Pricing
Build without counting projects.
Start free with up to five projects that never expire. Choose a paid plan when you need more room, with storage and database capacity shared across your account.
$0 / month
For the one that is not earning yet.
- 5 projects, and they never expire
- 1 GB object storage
- Managed database up to 250 MB
- Continuous database backups, and point-in-time restore free through Dec 1 (UTC)
- A fortly.com subdomain, with HTTPS
- Authentication, file storage and scheduled jobs
- Unlimited teammates
$7 / month
For the first one that has to stay up.
- Unlimited projects
- — sharing one pool of compute, not one each
- 10 GB object storage, pooled across your account
- Managed database, 1 GB pooled across your account
- Restore the database to any minute in the last 7 days
- 20 custom domains and subdomains, with HTTPS
- Authentication, file storage and scheduled jobs
- Unlimited teammates
$15 / month
For the ones that are earning.
- Unlimited projects
- — sharing one pool of compute, not one each
- 100 GB object storage, pooled across your account
- Managed database, 10 GB pooled across your account
- Restore the database to any minute in the last 7 days
- 20 custom domains and subdomains, with HTTPS
- Authentication, file storage and scheduled jobs
- Unlimited teammates
Paid plans include unlimited projects sharing your account’s compute, storage, and database allowances. Projects rest between requests. See plan limits and capacity options
What can I deploy?
Deploy static sites and supported JavaScript applications, connect a GitHub repository, or upload a ZIP or tar.gz archive. See framework support and build requirements.
What happens if a build fails?
Your current release keeps serving. The failed release stays in history with its build output, so you can inspect the error and deploy again. If it is your first deployment, the app becomes available after a successful release.
How does app-user authentication work?
Connect a trusted identity provider, then configure API roles, operation grants, and row policies. Fortly verifies app-user tokens for the Data API. Explore app-user access.
Can I bring my own domain?
Yes. Custom domains include HTTPS with certificates managed by Fortly, within your plan’s domain allowance. Every project also gets a Fortly address.
Can I take my data with me?
Export your database in PostgreSQL SQL, MySQL SQL, or JSON. Read about exports, restore, and compatibility.
Can an agent work with Fortly?
Authorize an agent from the console to use Fortly’s API with the access you grant it. Connect your agent.
FROM THE FIRST IDEA TO WHAT’S NEXT.
Make something.
Give it a home.
Your next project starts with a name. The rest stays close.