UlikaDocs
Open Ulika

Getting started

  • Ulika documentation
  • How Ulika works
  • Requirements
  • Quickstart

Connect a site

  • Connect from the dashboard
  • Connect with the CLI
  • Connect with an AI agent
  • Approving a connection
  • Private previews
  • The GitHub App
  • Connect Vercel

Integrations

  • GitHub integration
  • Vercel integration
  • Netlify
  • Claude Code
  • Codex
  • MCP tools

Editing

  • The editor
  • The style panel
  • Sections and pages
  • Mobile preview, autosave and drafts

Publishing

  • Publish your changes
  • History and restoring a version
  • When a publish fails

Team

  • Team roles
  • Inviting people

Projects

  • Project settings
  • Delete a project
  • Website code

Troubleshooting

  • Needs attention reasons
  • Vercel problems
  • GitHub problems
  • CLI errors and exit codes
  • Frequently asked questions

Security and privacy

  • Security and privacy overview

CLI

  • CLI reference
  • CLI changelog

Integrations

Netlify

What works today for a site hosted on Netlify, what the Available status in Ulika really means, and what is not supported yet.

Last updated October 10, 2026

Netlify is Available, not Connected, in Ulika. That wording matters: there is no Netlify account connection yet, but a site that is hosted on Netlify and built from GitHub can still be connected, edited and published. This page separates what is real today from what is not, so you can plan around it.

The short answer#

  • You cannot connect a Netlify account, token or API to Ulika. The Connect button for Netlify in project settings does not connect anything.

  • You can connect a site that Netlify builds from your GitHub repository. Ulika works with Netlify through your repository and through Netlify's GitHub App.

What works today#

CapabilityStatusHow it works
Detecting that a site is on NetlifySupportedThe site check recognizes Netlify from response headers (x-nf-request-id, a server header that names Netlify) and from *.netlify.app and *.netlify.com addresses. It shows Netlify under Hosting in the check details.
Connecting the site and installing the connectorSupportedThe connector's build step is started through netlify.toml. See below.
PublishingSupported for connectors using Git deliveryPublishing commits a content file to your default branch. Netlify rebuilds on that push like it does for any commit. No deploy hook is needed.
Seeing Netlify's build resultsSupported, with a GitHub permissionNetlify's GitHub App is on Ulika's list of recognized hosts, so Ulika can read the build results Netlify reports on GitHub. This needs Ulika's read-only permissions for commit statuses, checks and deployments.
Reading a Netlify preview addressSupported with limitsA preview address on netlify.app that Netlify reported through GitHub is accepted. Ulika never sends a Vercel bypass secret to it.

Ulika never talks to your Netlify account, so none of this is confirmed against Netlify directly. It is worked out from your repository and from what Netlify reports to GitHub.

How the build step starts on Netlify#

Ulika needs your Netlify build to run its build step. It does that by editing the build command in netlify.toml:

  • If your repository has a netlify.toml (and no vercel.json), the command line under [build] becomes node .ulika/build.mjs. Every other line stays as it was. Your original command is kept in .ulika/connector.json and runs unchanged inside the Ulika build.

  • If the repository has no netlify.toml, Ulika instead wraps the build script in package.json: your original script moves to build:site, and build runs the Ulika step. This only works if Netlify runs npm run build.

  • If netlify.toml has a build command Ulika cannot read safely (for example a multi-line value), Ulika stops and reports a configuration conflict instead of guessing.

  • If your [build] table in netlify.toml sets a base folder, Ulika uses it as the site's root and checks it against the folder your code lives in. A mismatch stops the connection with The hosting project builds from a different folder.

Warning

Ulika reads only what is in your repository. If your Netlify site is configured with a build command in the Netlify dashboard that skips the build script (for example vite build), Ulika cannot see it. The connector's build step then never runs, and your published content is not applied. Set the Netlify build command to npm run build (or declare the command in netlify.toml) before you connect.

What is not supported today#

ItemStatus
A Netlify account, token or OAuth connectionNot available. Nothing like the Vercel connection exists for Netlify.
Ulika creating environment variables or build hooks on NetlifyNot available. Ulika does not call the Netlify API.
Reading password-protected Netlify previewsNot possible. A Netlify password page counts as a private preview. See Private previews.
Seeing a failed Netlify production buildNot observed. Netlify reports production builds as commit statuses, which do not say which environment they were for. Ulika's automatic undo of a failed live build therefore does not trigger from a Netlify failure. See Approving a connection.
A Netlify environment on the projectNot created. In the current version, nothing records Netlify as a project's deploy provider, so the Environments tab shows the provider as No deploy target.

Older connectors and the Next.js App Router connector read a build token (ULIKA_BUILD_TOKEN) while the site builds. Ulika does not set that variable on Netlify. Without it, those connectors build from the content committed in your repository, so your published edits are not applied. New Vite and React connectors do not use a token.

How Netlify appears in the product#

Open Settings for a project and then the Integrations tab. Under Deployment you see:

  • Netlify, with the description "Alternative deploy target for projects hosted outside Vercel."

  • A Connect button instead of a Connected badge.

Clicking Connect shows the notice Netlify is not connectable yet, with the text "Available in the next release." Nothing is connected or changed.

The Environments tab can show a Netlify badge in principle, but its empty-state text ("Connect Vercel or Netlify so publishing has somewhere to land.") describes a connection that does not exist for Netlify yet.

Recommended setup for a Netlify site#

  1. Make sure Netlify builds the site from your GitHub repository on every push to the default branch.

  2. Make sure the build runs through npm run build, or declare the command in netlify.toml.

  3. Connect the site from the dashboard.

  4. When the banner Approve Ulika's updated GitHub permissions appears, approve it so Ulika can read Netlify's build results. See The GitHub App.

  5. Leave Merge automatically once the build passes unchecked (the default) and activate yourself, because Ulika cannot catch a Netlify production failure for you.

Learn more#

  • Requirements: all supported hosts.

  • Connect from the dashboard

  • Private previews

  • Integrations: Vercel for the best supported host.

Was this page helpful?

PreviousVercel integrationNext Claude Code

On this page

  • The short answer
  • What works today
  • How the build step starts on Netlify
  • What is not supported today
  • How Netlify appears in the product
  • Recommended setup for a Netlify site
  • Learn more
Ulika documentationFAQ · CLI reference · Terms · Privacy