A website that still opens is not necessarily easy to maintain after a change of provider. Questions about website vendor lock-in usually concern something practical: who controls the domain, which materials can be retrieved, and what is needed to move or repair the system?
Dependency does not always indicate bad intent. A managed package can reduce the owner's technical workload. The problem is discovering access limits, costs, and continuity arrangements only when the business needs a change. Understanding them at the proposal stage helps you choose suitable work, including when considering a custom website with me.
Separate the domain, website content, and underlying system
As an illustration, a store may need another provider because its previous technical contact is no longer available. The domain still works, but the owner does not know which account handles renewal. Product photographs can be downloaded, while order records are readable only through an application. Each part presents a different access need.
Start with a short inventory. Record who manages the domain, hosting, email, editor accounts, analytics, and payments where used. For each account, identify access holders, recovery routes, renewal responsibilities, and the authority granted to anyone assisting. Clear control of primary accounts does not mean every employee should share one administrator password.
The domain differs from hosting and website code. ICANN explains domain transfers between registrars and applicable conditions, including circumstances that can restrict a transfer. Changing registrar also differs from changing hosting. Check the registrar's rules and your domain type; one account change does not automatically move the website and its email.
Assess the delivery model before treating it as a problem
Some services provide a running website with ongoing management, others offer editing facilities, and some provide code and documentation under a separate agreement. Assess each package against the rights and work actually sold. Paying for website development does not, by itself, establish that every piece of code or third-party licence transfers to the customer.
A SaaS website builder uses an application operated by its provider. NIST's definition of SaaS distinguishes using an application from managing its underlying infrastructure. Not all SaaS products are website builders, and each product's export capabilities require examination.
Useful questions are what you can use while subscribed, what you receive when the relationship ends, and what must be rebuilt if you move. An article or catalogue export may not include the design, user accounts, payment facilities, or application functions. Conversely, receiving code does not establish that all supporting services are available on the destination host.
GOV.UK discusses cloud service benefits alongside dependency. Its guidance does not suggest removing every dependency. The relevant principle is to weigh the value received against the ability, cost, and time required to switch. Its context is cloud management, rather than a determination of your website's contractual rights.
Consider changing costs, features, and business needs
A low initial price needs to be read alongside renewals, storage, account limits, service usage, and additional features. Rates can change, including increases, under applicable terms and notice arrangements. Compare costs over the same period and scope, including data retrieval or rebuilding when leaving. Without that calculation, neither custom development nor a subscription can be described as always cheaper.
Check page limits, data formats, integrations, and content policies too. If a feature is withdrawn or a policy changes, would the way you present products or receive enquiries change? The answer depends on the selected product. These are considerations before purchase, not predictions that every platform will impose tighter restrictions.
Business changes make these questions more useful. An additional branch may need a location page with a different contact; a new product line may need a way to compare specifications. A design's value lies in meeting those needs. Various platforms support your own domain, so the domain alone is not the main distinction of a custom website.
Who can see website data and analytics?
Public material differs from visitor statistics, customer messages, transaction records, operational logs, and administrator access. What a provider can see depends on architecture, permissions, settings, and policies. Technical access does not automatically grant a right to use data to build another product; managing the system is not evidence that a provider will copy your business.
If analytics or forms are used, ask about collection purposes, recipients, retention periods, and export or deletion options. Check who manages the account and what happens to data when the service ends. A custom website using third-party hosting, analytics, or messaging also has data flows that need to be understood.
NCSC emphasises understanding risks, establishing control, checking arrangements, and ongoing improvement in supply chains. For website decisions, this supports asking how supporting services are managed. The reference does not certify that a particular provider meets all of those principles.
If the provider stops operating, what can continue?
An outage, service discontinuation, or provider closure can affect a dependent website. The impact follows the component used: an analytics outage does not necessarily stop public pages, while reliance on a booking service can interrupt that function. Identify critical functions and who can help restore them.
Discuss backup formats, storage locations, available access, and the recovery work included in the agreement. A file copy alone does not prove that the website can run again. If a recovery test is included, agree on a separate environment, permitted data, and how results will be assessed without disrupting the active system.
A move can require code changes, new licences, data transfers, and checks on email or payments. Downtime and data changing during the move also need planning. Do not cancel the previous service merely because the new homepage opens; important functions and necessary access need checking first.
Custom website value lies in decisions you can discuss directly
With my custom website service, you explain requirements to the person doing the development. As a web engineer and technical lead, I help translate materials, priorities, and visitors' tasks into a work scope. For a company with several service lines, for example, we can plan page relationships and contacts around its business process.
The benefit is room to discuss design, updates, and further development according to actual needs. These still depend on technical feasibility, time, and cost. Editing facilities, particular documentation, maintenance, and migration assistance need to be included in the offer where required; they are not automatic facilities.
Source code is not included by default in my service, may require a separate offer, and is not always available for handover. Content rights, domain accounts, licences, and the ability to move are also discussed separately. Custom websites can still depend on third-party services. The reason to choose me is clarity about decisions and agreed work, rather than a promise of freedom from vendors or ownership of every component.
Why does an engineer still need to review AI output?
AI can help create designs and code without recognising every project dependency. A product page might look complete while its button still uses a demonstration service or its form has no correct recipient. OWASP discusses incorrect AI output, including unsafe code suggestions. Confident wording does not establish that the system is ready for use.
An engineer assesses the output against requirements and checks agreed functions. When a move is discussed, that includes identifying services still needed and whether replacements can perform the same functions. Customer data, account access, and private logs should not enter an AI tool without assessment of the task, permissions, and tool terms.
Building with AI yourself can be suitable if you can assess code, test flows, and maintain the result. My service provides direct technical discussion and review. AI used during development also differs from a paid AI feature running on the website; if such a feature is planned, usage costs and controls need separate assessment.
Bring these questions before accepting a proposal
- Which work products are handed over, including access, materials, documentation, and code where available?
- Who manages the domain, hosting, email, and their renewals?
- Which licences remain tied to the provider, and what would need repurchasing after a move?
- Which data can be exported, in what format, and how can important functions continue?
- What are the limits on updates, support, recovery, additional charges, and service termination?
If the website already exists, gather agreements, invoices, account lists, and access information you are authorised to manage. Do not share passwords in an initial message. Disputes about rights or handover require assessment of the documents and appropriate parties; changing providers does not automatically resolve them.
You can discuss your website or further development needs with me. Start with functions to retain, the problem encountered, and the access information available. The proposal can then be assessed through its work and limits, rather than appearance or introductory price alone.
Frequently asked questions
Does paying for a website mean receiving all source code?
Not automatically. Work products, code, usage rights, licences, and documentation follow the agreement. My service does not include source code by default; it may require a separate offer and is not always available.
Is a custom website free of dependencies?
No. A custom website can use hosting, licences, APIs, or other third-party services. Assess its value through requirements, scope, management, and development options rather than a promise of freedom from vendors.
Can a platform provider use all website data?
Access capabilities and usage rights differ. Check architecture, permissions, settings, and policies for purposes, recipients, retention, and export. Managing a system is not evidence that the provider will copy the business.
Is exporting content enough to change hosts?
Not necessarily. Exported articles or a catalogue may omit design, accounts, or application functions. A move requires assessment of formats, licences, available code, supporting services, compatibility, costs, and testing.
