Separate the roles: names, records, runtimes, and data
A gives your project a name. A registrar handles registration and renewal, a DNS provider maintains its records, a deployment platform serves pages and runs programs, and a database or file store saves data. Different companies can handle these roles, or one company can provide several.
Consider a shared task list: NameSilo manages the registration of example.com, while Cloudflare DNS points www.example.com to the frontend on and api.example.com to the backend on . After loading the interface, the browser calls the API; the backend accesses the database.
This is one possible combination. An information page can start with static hosting, and a task list used only in the current browser may use local storage. Platforms commonly provide a default domain, so buying a custom domain is not a prerequisite for testing your first version.
Changing registrars changes who manages the name's registration. Moving an API changes where the application runs. Updating the relevant records and configuration correctly lets the original address keep working.
Take this with you · Identify each service's responsibility before deciding which ones your project needs.
Buying a domain: NameSilo, Cloudflare, and comparison tools
Registering a domain normally grants use for a limited period that you renew. A handles registration, renewal, and transfers. In example.com, .com is the top-level domain; www.example.com is a subdomain that the holder usually configures without a separate registration fee.
NameSilo is a useful comparison starting point, but value depends on the extension, promotions, and renewal terms. Cloudflare Registrar offers at-cost registration and renewal for supported extensions. Domains registered there must use Cloudflare nameservers; switching to another DNS provider requires transferring to another registrar.
TLD-List and Domcomp compare registration, renewal, and transfer prices. Pick an extension, then compare three-year cost: the first registration plus two renewals. Check premium-domain renewals separately. Comparison sites provide leads; confirm currency, promotion conditions, and extra charges at the registrar's checkout.
Set renewal reminders or auto-renewal and maintain access to your account and contact email. NameSilo includes WHOIS privacy for eligible extensions to reduce public registration information; this does not replace account security or apply to every extension. Links to both registrars and comparison tools appear below.
Suppose registration costs 2 units and renewal costs 30 per year: three years cost 62. Another offer at 12 per year costs 36. These invented prices illustrate why the cheapest first year can cost more over time.
Take this with you · Compare extensions, renewals, and total holding cost rather than giving registrars a permanent price ranking.
DNS hosting: buy at NameSilo, configure at Cloudflare
You can renew at NameSilo while using Cloudflare for DNS. A typical setup adds the domain to Cloudflare, reviews imported records, then changes the at NameSilo to the ones Cloudflare assigns to that domain. Allow verification and caches to update. This changes the DNS hosting provider.
have distinct purposes: A points to IPv4, AAAA to IPv6, and CNAME to another hostname. MX identifies mail servers, while TXT often supports ownership verification and email authentication. Record values normally contain hostnames or IP addresses, not complete https:// URLs, page paths, or ports.
Save and check existing records before migration, including email MX/TXT records and subdomains; automatic scanning may miss records. If DNSSEC is already enabled, follow the official migration process to handle the old signing configuration before switching, then re-enable it after activation.
After adding a www CNAME at Cloudflare, you still renew the domain at NameSilo. When connecting Vercel, copy the actual values shown in that project's domain settings instead of reusing an old tutorial's IP address.
Take this with you · Changing nameservers changes DNS hosting; transferring registration is a separate operation.
Cloudflare: DNS, orange clouds, CDN, and HTTPS
Cloudflare has a generous reputation among independent builders because it offers free capabilities such as DNS, CDN, and basic website protection. Evaluate each product separately: free plans have a scope, and paid features, rule counts, and resource usage follow their own terms.
Gray-cloud DNS only answers lookups, so website traffic goes directly to the destination. Orange-cloud Proxied routes supported website traffic through Cloudflare before reaching the origin, enabling caching, protection, and redirects. Not every record or protocol can be proxied; follow your hosting platform's domain instructions.
uses TLS to encrypt transport and verify service identity. With a proxy, consider both browser-to-Cloudflare and Cloudflare-to-origin connections. For a conventional HTTPS origin, configure a valid certificate and Full (strict) validation. Diagnose certificate errors on the relevant connection, and avoid public caching of private or personalized responses.
A blog can use orange-cloud caching for public resources. A Vercel site can start with DNS only as directed by Vercel. Hosting DNS at Cloudflare alone does not send website traffic through its CDN.
Take this with you · DNS hosting and website proxying are separate settings; orange-cloud proxying brings the relevant website traffic through Cloudflare.
Gateway: control what connected devices access
is a secure gateway within Cloudflare One / Zero Trust, commonly used to manage devices' Internet traffic. DNS policies can block malicious domains, network policies filter by properties such as IP and port, and HTTP policies handle finer web requests. Authoritative DNS hosting and device DNS filtering serve different purposes.
Devices or networks must first send traffic to Gateway, for example through a configured Gateway DNS endpoint or Cloudflare One Client, which often appears in WARP tutorials. Putting your domain on Cloudflare does not automatically enroll your phone or computer. Verify traffic arrival through access results and Gateway logs.
DNS filtering sees domain queries, not complete encrypted URL paths or page bodies. Policies inspecting HTTPS content also require appropriate client trust certificates and TLS decryption. The separate AI Gateway product handles model API logging, caching, and rate limits. Identify which traffic you want to manage first.
Evaluate Gateway DNS policies to block known malicious domains on connected home devices. To share a webpage running on your computer, examine Tunnel next. To observe AI API usage, examine AI Gateway.
Take this with you · Gateway focuses on connected devices' Internet policies: connect traffic, then configure and verify the rules.
Tunnel and Access: reach an internal service, then control entry
uses cloudflared on your infrastructure to initiate an outbound connection to Cloudflare and forward requests to a local service. This helps when you lack a public IP or cannot configure inbound port forwarding. The machine must reach Cloudflare and keep both the application and connector running.
For an HTTP application, tools.example.com can route to a service the connector can reach. Visitors use that address and requests travel through the tunnel. The application still runs on its original machine; shutdowns, network loss, or a stopped application affect availability. Check separate client requirements for non-HTTP protocols.
adds identity and access policies in front of an application, such as allowing selected email addresses. When publishing a private admin page, configure and verify Access or the application's own login controls. Encrypting the tunnel does not automatically restrict who can open the page.
An internal reporting site can use Tunnel for connectivity and Access to admit team members. Verify that approved accounts get in, unauthorized visitors are denied, and the original machine's connection loss behaves as expected.
Take this with you · Tunnel supplies connectivity, Access supplies entry policies, and your chosen machine still runs the application.
More Cloudflare services: code, files, and bot checks
serves static assets and runs server-side code such as APIs, supporting small tools and edge request handling. As a platform, it manages underlying runtime resources while you supply code. Runtime compatibility and request and compute allowances still matter.
Pages also supports website deployment and appears in many older tutorials. At the time of this review, Cloudflare recommends Workers for new projects. Check your framework's support and deployment guide instead of assuming a conventional Node.js server runs unchanged in every environment.
R2 is for images, attachments, and backup files. D1 provides a SQL database, while KV stores key-value data; their models and consistency differ. Turnstile helps reduce automated form abuse, and AI Gateway observes and controls model API calls. Add capabilities as your project needs them.
Review free allowances per product. Workers compute, R2 storage, and storage operations have their own meters. R2's lack of egress bandwidth charges does not make all storage and operations free. Check usage and billing after launch.
An image guestbook might use Workers for pages and an API, R2 for images, a database for messages, and Turnstile when needed. A static introduction page usually does not need this entire combination.
Take this with you · Choose Cloudflare capabilities by the job: running code, storing data, controlling access, or reducing abuse.
Vercel: build, preview, and publish a frontend
hosts websites and frontend applications, including framework server rendering and Functions. A typical workflow imports a Git repository, checks the framework, project root, and build command, tests the platform URL, then connects a custom domain.
A lets you review branch or pull-request changes; production is the live release. Git integration commonly triggers deployments automatically, so identify the production branch. Verify forms, mobile layout, APIs, and persistence in the relevant environment, beyond simply loading the page.
configure values outside source code, such as an API address. Development, preview, and production can use different values; changes require a new deployment. Keep secrets on the server. Public values included in browser code are visible to visitors even when entered through a hosting dashboard.
Hobby is for personal, non-commercial use; check suitable plans for commercial projects. Functions have execution and resource limits. Match persistent workers, ongoing connections, or special dependencies to a suitable runtime product. Small full-stack projects can start on one platform and split when needed.
Share a task-list preview so friends can try adding, deleting, refreshing, and using a phone. Point previews at a test API and production at a production API, then confirm the configuration actually used before release.
Take this with you · Vercel connects builds, previews, and releases; verify configuration, runtime limits, and plan eligibility.
Fly.io: a configurable runtime for a backend
Machines start application VMs from , supporting APIs, custom runtime dependencies, and background workers. An image packages the program and dependencies. You still choose region, memory, instance count, processes, ports, and health checks.
A common workflow packages the backend, configures the application and secrets, deploys a Machine, checks its platform address and logs, then connects an API subdomain. Match the listening port to platform routing. Keep the API near its database and choose autostop or continuously running instances to suit the workload.
Data that must survive deployments belongs on a or in an independent database, rather than relying on the ephemeral root filesystem. Fly Volumes are local to a region and host; data is not automatically replicated between volumes. Plan sharing, replication, and backups before adding instances.
Fly.io bills for resources such as compute, storage, and networking, with a limited trial for new users. Historical free allowances are not a budget for a new project. Stopping a Machine does not stop every charge, including volumes. Start small and check which resources still incur costs.
A Python API with specific system dependencies and a background worker may fit Fly.io. SQLite data needs a persistent volume plus a backup and multi-instance write strategy; connecting an independent database is another option.
Take this with you · Plan backend runtime, persistent data, availability, and ongoing costs together.
Connect the pieces with a verifiable launch plan
Choose a small combination for the scenario: Vercel or Workers for an information site; Fly.io when an independent API is useful; Tunnel and Access for an existing internal service; Gateway for device Internet filtering. A project rarely needs every product from the start.
Follow the access path: valid domain registration → nameservers at the actual DNS provider → records matching the hosting platform → domain binding and HTTPS → the page calling the right API → correct backend data access. Test the default platform URL before the custom domain to isolate failures.
www.example.com and api.example.com are different origins. The backend must configure for browsers to read cross-origin responses; logins also require correct cookies and credential handling. CORS does not replace API authentication. A production browser API URL pointing at localhost targets the visitor's own device.
Verify first visits, failed submissions, persistence after refresh, access from target regions, and deployment rollback. Rolling back code does not usually roll back database contents. Keep monitoring domain renewal, usage, and bills. Include these requirements in your AI brief to get an appropriate deployment plan.
A shared task list could combine NameSilo registration, Cloudflare DNS, a Vercel frontend, a Fly.io API, and an independent database. A personal offline list may already meet its goal with local HTML and browser storage.
Take this with you · Test the request path and include data, access, rollback, and costs in the deployment brief.
You bought a domain at NameSilo and want a Vercel frontend, a Fly.io API, and Cloudflare DNS. Which statement is correct?
Choose an answer before reading the explanation.
Write a domain-to-deployment brief for your project and ask AI to explain responsibilities and verification.
Think first, then uncover help as needed. Later chapters expect more complete descriptions and clearer checks.
Bring this chapter's context to your AI. Going deeper is optional; you can keep reading without it.
Explain registrars, DNS, CDN, hosting, and databases using a small-shop analogy, then point out where that analogy breaks down.
One approach you can make your own
I'm learning computers and AI-assisted programming from scratch. In this chapter I learned: Domains and hosting：Separate domain registration, DNS hosting, application deployment, and data storage；Compare registration, renewal, and multi-year costs, and explain the NameSilo–Cloudflare combination；Distinguish Cloudflare DNS, website proxying, Gateway, Tunnel, and Access；Choose a runtime for a frontend, API, or persistent worker and write a verifiable deployment brief Explain registrars, DNS, CDN, hosting, and databases using a small-shop analogy, then point out where that analogy breaks down. Check my understanding first. Explain one small question at a time with a concrete example and the limits of any analogy. Ask a scenario question, then adapt to my answer. Distinguish facts, guesses, and uncertainty; suggest hands-on ways to check. Confirm the version before giving tool-specific advice, and don't invent features or references.
Complete this chapter
Mark the sections as read and finish the required activities listed below to record completion. You can visit the next chapter at any time.
Read the original references
This is an introduction. These official resources help you check details and explore further.
Domains · NameSilo registration, renewal, and transfer pricesDomains · NameSilo WHOIS privacyComparison tool · TLD-ListComparison tool · DomcompDomains · Cloudflare RegistrarDomains · Cloudflare supported extensionsDNS · Nameservers and Registrar restrictionsDNS · Cloudflare setup and DNSSEC migrationDNS · Record typesCloudflare · Website plansCloudflare · Proxied and DNS-only recordsHTTPS · Full (strict) origin validationGateway · Traffic policiesGateway · HTTPS inspection and certificatesTunnel · Publish local servicesAccess · Application access controlsDeveloper platform · Workers, D1, and KVDeveloper platform · Pages and new-project guidanceDeveloper platform · Workers pricingStorage · R2 overviewStorage · R2 pricingForm protection · TurnstileModel requests · AI GatewayVercel · Preview and production environmentsVercel · Environment variablesVercel · Hobby plan eligibilityVercel · Functions limitsFly.io · MachinesFly.io · Volumes and data boundariesFly.io · Resource pricingFly.io · New-user trialConnecting frontend and backend · MDN CORSOnce the service is online, where should its data live, who can change it, and how is it backed up? Next, explore data and storage.