Working with Netlify?

Netlify deploy broken or bill climbing? We fix it.

Most Netlify sites that reach us were set up quickly by someone else and have been limping along since. Build logs nobody reads, redirects that almost work, a forms inbox full of spam. We find the specific setting that is causing the trouble and sort it.

  • Since 2015Fixing technology
  • FreeEstimates
  • US teamReal engineers

deploy.log

still failing

What it is

Netlify at a glance

Netlify is a hosting platform built around the Jamstack pattern: build a static site in CI, push it to a global CDN, then add Functions for dynamic pieces, Forms for lead capture and Identity for signed-in users. It was founded in 2014 by Mathias Biilmann and Christian Bach and is headquartered in San Francisco.

The product has grown well past static hosting. Edge Functions run close to the visitor, Netlify Blobs handle small bits of state, and an Image CDN resizes on the fly. It competes with Vercel, Cloudflare Pages, GitHub Pages and AWS Amplify, and it is where many AI-builder tools send their output by default.

Type
Front-end and Jamstack cloud
First released
2014
License
Proprietary SaaS; Netlify CLI open source
Maintained by
Netlify, Inc.
Typically used for
Static sites, SSG frameworks, marketing sites, Jamstack apps, headless-CMS frontends, AI-builder deploys

The honest version

Netlify pros and cons

No technology is all upside. This is where Netlify earns its place and where it tends to cause trouble.

Where Netlify is strong

  • Git push and it is liveConnect a repository and every push builds and deploys on its own. It covers Astro, Hugo, Gatsby, Jekyll, Next.js, Nuxt and Eleventy without extra configuration in most cases.
  • A free tier that actually goes somewhereSmall marketing sites and side projects can run without a bill for a long time. Teams can get real work done before they hit a paid plan.
  • Batteries includedForms capture submissions without a back end, Functions wrap AWS Lambda, Edge Functions run at the edge, and Split Testing sits on the same dashboard.
  • Deploy previews for every pull requestReviewers get a working link instead of a screenshot, which makes catching broken redirects and missing images easier before they ship.
  • A strong CDN and a friendly dashboardThe global edge is fast, and the admin interface is one of the clearer ones in this space. Non-engineers can find what they need without a walkthrough.

Where Netlify bites

  • Bandwidth overages are not gentleThe included 100GB covers a surprising amount of traffic until a video, a large image set or a scraper changes that. Overage billing at $55 per 100GB catches people out.
  • Build minutes and function limits bite paid plansA noisy build that keeps retrying burns through the monthly allowance quickly. Functions are capped at a 10MB bundle, which rules out some common libraries without extra work.
  • Forms spam filtering is a blunt instrumentThe built-in filter either lets junk through or quarantines real leads, and digging through quarantine by hand gets old fast.
  • AI-builder output often misconfigures redirectsSites generated by Bolt, Lovable and similar tools frequently ship with broken rewrites, missing headers or a publish directory that does not match the build.
  • Inherited sites have stale build settingsAn old Node version pinned in the dashboard, a deploy key tied to someone's personal account, environment variables nobody documented. Deploys keep working until one day they do not.
  • Next.js has rough edges hereThe Next.js runtime on Netlify has improved but still trails Vercel for the newest features. Image optimisation and middleware behaviour sometimes need manual fixes.
  • Identity is on life supportnetlify-identity-widget is in maintenance mode only. New auth work should not start on it, and existing sites using it need a plan to move off.

Sound familiar?

Common Netlify problems we fix

The Netlify problems that bring people to us, and what you have once each one is fixed.

Build exceeded 30 minutes

The deploy keeps failing

Usually a build that installs too much, a Node version mismatch, or a publish directory that does not match what the framework actually produces.

Deploys green and under ten minutes

350GB of 100GB included

The Netlify bill jumped

A single large asset going viral, a scraper hammering the site, or unoptimised images being downloaded on every page view.

Traffic understood, bill back to normal

spam quarantine: 4,812

Forms are drowning in spam

The built-in filter does not stop modern bots, and genuine submissions get mixed in with the noise.

Spam filtered, real leads delivered

_redirects line 24 invalid

Redirects and rewrites nearly work

Common with sites handed off from an AI builder or a previous developer. One rule is wrong and half the routes break.

Redirects reviewed and tested

bundle exceeds 10MB

A Function will not deploy

A dependency that pulls in too much, or code that should have been split across several smaller functions.

Function trimmed and deploying

admin user: unknown

The previous developer vanished

The Netlify team is in their name, the deploy key is on their GitHub account, and nobody has the login for the DNS.

Every account back in your name

CNAME flattening not set

The apex domain does not resolve

DNS pointed somewhere Netlify cannot follow, or an old A record left behind from a previous host.

DNS cleaned up and verified

What we do

Netlify help, from rescue to upkeep

Call us for one failing deploy, or hand us the whole account.

Rescue
Builds failing, redirects broken or a site handed over with no documentation. We get it deploying again first and tidy the settings second.
Cost control
Find where the bandwidth is actually going, cache and optimise what is worth keeping, and move what is not off Netlify.
Forms and spam
A proper filter in front of Netlify Forms, or a move to a form backend that matches how your team actually works with leads.
Migrations
On to Netlify from another host, off to Vercel or Cloudflare if that fits better, with the DNS cutover planned rather than hoped for.
Framework work
Astro, Next.js, Nuxt, Hugo and similar. Build pipelines that finish quickly and produce what the CDN expects.
Managed Tech
Monitoring deploys, DNS and bills, with a team to call, on an ongoing basis.

How it works

From first message to fixed

  1. Look Free estimate

    Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.

  2. Fix

    We fix the cause, not the symptom. If something is down, getting it back up comes first.

  3. Harden

    Backups, monitoring, updates and access, so the same problem can't quietly come back.

  4. Hand back or stay on

    You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.

Often found together

Running Netlify alongside something else?

We work on the whole stack, so the problem can be wherever it actually is.

Questions

Netlify questions

Something else? Call+1 737 727 7327

Why is our Netlify deploy failing?

The common causes are a Node version that does not match the project, a publish directory that does not match what the framework outputs, a build that runs past the 30 minute limit, or an environment variable that was set on someone's personal account and is now missing. The build log usually points at the cause once you know where to look.

Can you take over a Netlify site from a previous developer?

Yes. We move the Netlify team, the Git deploy key, the DNS and any environment variables into accounts you own, document what each one does, and make sure deploys still work at the end of it.

Why did our Netlify bill jump?

Almost always bandwidth. Either a large asset started getting a lot of traffic, a bot is scraping the site, or images are being served at full size on every page view. We find out which and either cache it properly or move it off Netlify.

Should we move from Netlify to Vercel (or the other way)?

Sometimes. Next.js sites often run better on Vercel for the newest features, while content-heavy static sites and small teams often get more from Netlify's free tier and dashboard. We will tell you plainly which fits your site rather than selling you a migration for its own sake.

Can you clean up Netlify form spam?

Yes. We put a proper filter in front of the form, tune the honeypot and challenge settings, and in some cases move submissions to a dedicated form backend so your team sees real leads only.

How much does Netlify help cost?

Estimates are free. Tell us the site and what is going wrong and you get a price before any work starts.

Free estimate

Netlify giving you trouble?

Tell us what you're running and what's going wrong. A person reads it and comes back with an estimate.

  • No charge to find out what it will take
  • If it's urgent, say so

Replies come from a person. By sending, you authorize us to email you back. No marketing.