Netlify

Netlify is a managed platform for deploying websites and web applications from source code or prepared builds. It combines frontend delivery with serverless services and deployment workflows. Applications need to fit its supported build and runtime model; it is not a general-purpose VPS with operating-system access.

Key features

• Git deployments. Repository-based workflows connect source changes to builds and deployments.
• Deploy previews. Preview environments let teams review changes before production publication.
• Functions and storage. Serverless functions and platform data services complement frontend hosting.
• Edge delivery. Custom domains, SSL and a global delivery network support published applications.

Who it is for

Frontend developers, product teams and agencies working with modern web frameworks, marketing sites and applications that fit a managed build-and-functions architecture.

Pricing at a glance

A free plan has bounded monthly credits. Paid plans add allowances and collaboration features, with usage measured across several activities. Read the current credit model, recharge options and limits rather than assuming older bandwidth-only pricing still applies.

Pricing model checked on 15 October 2026; confirm current terms on the official product page. No currency conversion or fixed price estimate is used in this profile.

Things to consider

• Production deployments, compute and requests can consume the same credit budget.
• Long-running backend processes may need a separate hosting architecture.
• Framework support and function limits should be checked before migrating an existing application.

Before moving a production workload, record its runtime versions, storage needs, database size and external services. Decide who will own updates and incident response. A small pilot is a better way to establish compatibility than relying on a headline feature list; include a restore exercise and check that the team can retrieve its data independently.

Getting started

1. Read the official documentation and plan information, then write down the features and costs your project needs.
2. Choose a small test environment that matches the application’s runtime and persistent-data requirements.
3. Configure restricted access, domain settings and certificates; keep secrets out of source repositories.
4. Test deployment, backups and restoration with representative data before changing production DNS.
5. Review usage and recurring charges after the pilot, and document a migration or cancellation path.