Choose an identity and test the access it receives.
Connected resources
Reach KV, files and email from the live binding inventory.
03 / OPERATE
Know what shipped. See what happens next.
Follow application output and explore traffic without losing the selected
project. When a job fails, its next step stays close to the outcome.
Read one release’s build output or the app’s runtime feed. Inspect chart
values with a pointer, keyboard or data table. Keep the details you need
to investigate.
Separate deployment work from application messages.
Traffic you can inspect
Select a point, view the data and export measurements.
Jobs and email activity
Inspect the timer, recipient and result behind an event.
04 / RECOVER
An earlier moment. A considered way back.
Choose a point inside your database’s recovery window. Review the project
and time, follow the recovery and verify the result with the previous copy
retained.
Every plan has continuous backups. Pro and Max include point-in-time
restore; Free can use the offer through December 1, 2026 (UTC), once per
project in a rolling 24 hours.
A familiar editor for your blog or website, with content stored in
your project’s PostgreSQL database.
PHP runtime
PostgreSQL
File storage
Project address
Before you deploy+
Choose a site title, admin username, email and password. Fortly
installs the bundled WordPress code and creates its database tables.
Installing or updating themes, plugins and core from the WordPress
dashboard is not supported. For media, upload through Fortly Storage
and insert the public URL; dashboard media uploads are not
supported.
Connect triggers and services in a visual workflow editor. Keep
workflows and saved credentials in your project’s database.
Node.js runtime
PostgreSQL
Project address
Generated encryption key
Before you deploy+
No install fields are required. Open the app immediately after
installation to create its first owner account. Fortly generates its
credential-encryption key for the project.
In-process interval timers do not wake a sleeping project. For
scheduled workflows, use a webhook trigger and a Fortly HTTP
schedule that calls it.
See visitors, pages, referrers and countries without cookies or a
consent banner. Every visit is stored in your project’s database.
Workers runtime
PostgreSQL
Project address
Admin password you choose
Before you deploy+
Choose an admin password of at least 12 characters. Fortly creates
Umami’s tables and replaces its well-known default login before the
app is reachable. Sign in as admin.
Add a website in Umami, then paste its tracking script into your
site. Visitor locations come from Cloudflare’s country, region and
city, so there is no GeoIP file to keep current.
Shopify Storefront, Ghost, Strapi, Directus, Metabase, Appsmith,
Plausible and Uptime Kuma are catalogue previews. They do not have
one-click installers on Fortly yet.
Previewing one does not create a project or guarantee that its
unmodified source will run. WordPress, n8n and Umami are the available
installers today.
Fortly builds and adapts the server output to its Worker runtime.
Next.js static exports publish as files. If a Nuxt, Nitro, Analog,
React Router or TanStack Start build fails for Workers, it is retried
as a Node app.
Generated HTML, CSS and JavaScript deploy as files. Astro, SvelteKit,
Qwik and Angular render on the server with their Cloudflare target,
and Astro, SvelteKit and Angular with their Node target too.
Deploy JavaScript or TypeScript with a supported wrangler config. Go
with workers-go and Rust with workers-rs compile to WebAssembly for
the Worker runtime.
Choose the folders to deploy. The first is the project’s application;
each other becomes a service with its own address, releases and
variables, sharing one database, one set of users and one storage
space. A push rebuilds every service on that branch.
Requires @sveltejs/adapter-cloudflare as a dependency.
Qwik SSR
Requires adapters/cloudflare-pages/vite.config.ts,
generated by Qwik’s Cloudflare Pages setup.
Angular SSR
Requires a server bundle with
ssr.experimentalPlatform set to
"neutral" in angular.json.
Go and Rust
Target the supported Worker runtime with workers-go or workers-rs.
Ordinary Go or Rust server processes are not supported.
Python and other servers
Python Workers cannot publish to the shared production runtime yet.
Arbitrary Python, Ruby or PHP server processes are not supported;
the curated WordPress template has its own PHP runtime.
Browse the app catalogue, review setup and check which installers are
available before creating a project. WordPress and n8n have documented
installers; previewing another app does not mean it can be deployed in
one click.
Choose a GitHub branch or an archive, review build settings and follow
Source, Build and Publish. Inspect a failed attempt without losing the
release already serving. A later push can start the next release.
Create real PostgreSQL tables, inspect records, manage database objects
and connect them with foreign keys. Keep the visual relationship diagram
tied to the constraints enforced by the database.
Review table operations, application roles, trusted user identity and
row policies. Keep the table’s API request tester alongside the permission you are
testing; a publishable key does not itself identify an application user.
Continuous backups retain a seven-day recovery window. Review a full
date and timezone, follow the rebuild and switch-over, and inspect the
previous database’s expiry before Undo. Application code stays separate.
Choose private S3 buckets with scoped keys, app connections and temporary
downloads. Public Project files and Worker
folders keep their existing URLs. One shared storage allowance tracks
committed files, uploads and cleanup. Monthly read/write and transfer totals make bucket activity visible; smaller plans must still cover stored and reserved bytes. Separately enabled CDN delivery caches signed downloads or confirmed public asset folders while keeping S3 private.
Deliver signed private links or explicitly publish one folder. Review scope, cache lifetime, purge, pause and delivery budgets beside the bucket. Inspect request/byte charts, cache reasons, timings and privacy-safe request IDs. Every cache hit still checks current access; the S3 origin remains private. Available on hosted Fortly, with account-wide delivery limits.
Read flags, cached responses and expiring values through project-scoped
namespaces. Inspect values and JSON metadata in the console, preserve
expiry while editing, and use the same keys from Worker bindings or the
API.
Deploy supported hand-written wrangler Workers with assets, config
values, secrets and supported service bindings. Inspect the live
resource inventory and open the exact namespace or bucket behind a
binding.
Run a GET request on a cron timer or call a Worker’s scheduled handler.
Inspect next runs and outcomes, pause a timer during maintenance and
follow failures into runtime logs. Both paths use UTC.
Send outbound notifications to confirmed destinations. Follow ownership
and DKIM verification, inspect each Worker’s restrictions and review
delivery activity. Incoming routing and arbitrary-recipient delivery are
outside the current feature.
Open the selected release’s build output, separate runtime logs from
deployment events and inspect traffic with keyboard controls, a data
view or CSV export. Empty and unavailable measurements stay explicit.
Add a custom hostname, follow the DNS instructions and verify domain and
certificate readiness. The project’s default Fortly hostname remains in
view while you configure a domain within your account’s allowance.
Choose build, runtime or both for a saved value. Runtime overrides can
replace wrangler vars; secrets are encrypted at rest and should stay out
of repositories and browser code. Review reserved names before saving.
Invite teammates and assign owner, admin or member access as documented.
Account membership, application-user identity and public Data API roles
are different boundaries; granting one does not silently grant all the
others.
Connect an MCP client through browser sign-in and approve the projects
it may read. The integration is read-only and does not reveal secret
values. Review or revoke connected access from the console.
Review pooled file and database storage, project capacity, custom-domain
allowance and email quota. Capacity previews explain additional
resources; a full slot indicator is not a claim that existing
applications stopped serving.
TM
