Summary
- 4D INC matters where a buyer is not buying a fashionable database label but an implementation-support and service-continuity account: licences, maintenance, partner access, training, product updates, local help, application memory and the avoided cost of replacing a working custom system.
- The public evidence supports a real operating footprint. 4D lists 4D Inc. in Campbell, California, as its U.S. office, gives a global group footprint, publishes U.S. prices for 4D Server, desktop, expansion and partner subscriptions, and describes technical support, professional services, training, customer references and a public developer presence through official pages and GitHub.
- The price is disciplined by substitutes. A buyer can compare 4D Server and partner subscriptions with Claris FileMaker, Microsoft Power Apps, Mendix, OutSystems, a larger integrator, an internal team, a direct cloud database stack, or simply deferring automation. Those alternatives are not identical, but they keep renewal conversations honest.
- The important facts still missing from public evidence are private: renewal rate, paid account count, gross margin, partner concentration, support response time, incident history, customer concentration, the age and complexity of installed applications, and how often customers leave after a failed handover or version upgrade.
The renewal call prices memory, not a product name
Start with a failed handover at a small manufacturer, private clinic, distributor, school, membership association or professional-services firm. The original developer has retired, the internal operations manager knows which menu fixes month-end invoices, a new contractor is trying to understand why a form writes to three tables, and finance has a renewal quote on the screen. The cheaper substitute is easy to name: put the next project into Microsoft Power Apps, buy a packaged SaaS tool, hire a larger integrator, move the data into a cloud database, or freeze automation for another year. The hard question is not whether a modern alternative exists. It is whether the company can afford the disruption of removing a system whose configuration has become part of its operating memory.
That is the unit 4D INC sells in the United States and English-speaking North America. The buyer buys the right to keep developing and running 4D business applications, plus the support, maintenance, training, partner access, documentation and product-update path around those applications. 4D's own site describes 4D as a development platform for business apps and says it lets developers build web, mobile and desktop applications around a data model and business rules (https://us.4d.com/). Its U.S. store frames the commercial unit as deployment licences for business applications, partner programs and training rather than a single consumer app (https://store.4d.com/us/index.shtml).
The unit is costly because the invoice is only the visible part of the account. A 4D Server subscription can be cheap enough to renew compared with a full rebuild, but the true cost includes developer scarcity, version upgrades, testing, operating-system changes, user retraining, data cleanup, reports, backup habits, third-party integrations, support relationships and institutional knowledge. Public evidence can show prices, terms, product claims, support language, customer references, network records and review chatter. It cannot prove whether a given customer's application is well built, whether the local developer is competent, whether the support queue is fast, whether the buyer is locked in by habit rather than value, or whether 4D's private retention economics are healthy.
That uncertainty is the heart of the judgement. 4D is not a hyperscale cloud vendor with transparent segment revenue, published service metrics and investor disclosures. It is a long-running private software group with local sales and support surfaces. The public footprint tells an analyst how the account is sold and where the switching cost may arise. It does not let the analyst measure margin or renewal quality directly.
The right comparison is therefore not "old database versus new database." It is an account comparison. One side is a working custom application with accumulated configuration memory and a known support route. The other side is a substitute that may offer cheaper per-seat software, broader labour availability or fresher user experience, but only after the buyer pays the transition cost. 4D's economics improve when that transition cost is high and the existing system remains useful. They weaken when the custom application is poorly documented, the developer base thins, the buyer needs integrations that 4D cannot support, or a packaged SaaS workflow finally becomes good enough.
4D Inc is the local front of a global product group
The public company identity is clearest on 4D's own worldwide page. It lists 4D SAS in Le Pecq, France, as the group headquarters and lists 4D Inc. at 1821 S Bascom Avenue #433, Campbell, California 95008, with a U.S. phone number (https://us.4d.com/4d-around-the-world). That matters because the assigned entity is 4D INC, the U.S. company, while much of the product, legal and website evidence is group-level 4D evidence. The U.S. buyer sees a local commercial office and phone number, but the product owner, copyright notice and legal notices point back to 4D SAS.
The group describes a long operating history. The about page says Laurent Ribardiere created 4D in 1984 to simplify professional application creation with a graphical relational database, and it presents 4D as having customers on five continents, subsidiaries in more than ten countries, more than 10,000 customers, more than one million users, 100 countries, five subsidiaries, seven languages and 170 employees (https://us.4d.com/about-us). Those figures are company-published, not audited public financials. They still show that 4D is not a newly created shell around a single tool; it is a durable niche product group with a multi-country support promise.
The U.S. role is distribution, support and account continuity. The contact page gives the same U.S. phone number as the technical-support page, and the support page tells end users that their first contact should normally be the developer who created the solution, while 4D is available to help if needed (https://us.4d.com/contact-us and https://us.4d.com/4d-technical-support). That sentence is economically revealing. 4D does not appear to sell only direct vendor support to every end customer. It sits in a channel where developers, partners, software publishers and internal teams create the application, while 4D supplies platform rights, updates, partner programs, technical resources and escalation paths.
This channel structure makes the paid unit more complicated than a seat price. The end buyer may pay a local developer or integrator, buy 4D licences, maintain a server, purchase training, renew maintenance, and rely on 4D's documentation and product releases. The seller's value is not only code. It is also the continuity of a small ecosystem. If the local developer has kept good notes and the application is stable, 4D can be an economical way to keep a bespoke workflow alive. If the local developer disappears and the application is brittle, the same ecosystem can feel like a constraint.
4D's own audience segmentation supports that reading. Its homepage addresses decision makers, developers, software publishers and education customers (https://us.4d.com/). The developer page says a Bronze Partner subscription gives access to 4D Developer Standard, suitable for building internal applications, and says deployment requires 4D Server or 4D Desktop subscriptions or purchases (https://us.4d.com/4d-development). The software-publisher language matters because 4D applications may be packaged and sold by third parties. That multiplies the number of end users whose service experience depends on 4D while also making public customer counts less precise.
The company is private, so public readers should resist a false precision that the sources do not support. There is no current public income statement showing U.S. revenue, no partner-by-partner renewal data, and no disclosure separating 4D Inc. North American margin from group product economics. The article therefore treats group-level product evidence as context for the U.S. company, not as proof of the U.S. unit's profitability.
The product account bundles a database, runtime and labour path
4D's product promise is unusual because it bundles database, language, application runtime, web access, document features, spreadsheet features, mobile extensions and support resources. The "Why 4D" page says 4D is a platform that lets developers focus on data model and business rules, runs application code natively on macOS and Windows, and lets 4D Server run applications for desktop, mobile clients and web users (https://us.4d.com/why-4d). That is not the same as buying a managed cloud database. It is closer to buying a full-stack environment that keeps application and data decisions inside one vendor's world.
For buyers with small teams, that integrated world can be the attraction. 4D says the platform offers an IDE built around a database engine, a proprietary language, many APIs, programmable word-processing and spreadsheet tools, backup and restore, automatic updates and data encryption during transfer (https://us.4d.com/why-4d). A buyer does not need to assemble a separate database, backend framework, desktop runtime, reporting module and document engine if the 4D application already does the job. The economic benefit is fewer moving parts and fewer specialists.
The same integration is also the risk. A customer that has built years of forms, reports, menu logic, security rules and data procedures inside 4D may have fewer external developers who can take over quickly. The customer may own its data and business requirements, but the practical know-how lives in a specialised environment. That is why the renewal call is less about the brand name than about the availability of people who can keep the application alive.
Deployment language reinforces the continuity account. 4D says 4D Server can launch business applications for users connecting through Windows, macOS, web browsers, Qodly applications or mobile apps, and that server administration such as backup and memory optimisation is handled automatically (https://us.4d.com/deployment). It also says 4D Server can communicate with web services on other platforms and office applications. These claims are self-published and should be tested by the buyer, but they show the intended economic role: reduce the need for a large operations team.
The web-modernisation pitch follows the same logic. 4D Qodly Pro is presented as a way to give browser access to an existing 4D application while keeping business logic and project structure familiar, with "no new web frameworks" and "no migrations" (https://us.4d.com/4d-qodly-pro). A buyer deciding whether to renew should read that as a switching-cost argument. If 4D can extend an existing application to the web without a full rebuild, it protects old implementation memory. If it cannot meet the buyer's web needs, the account becomes easier to replace.
The product-release page also matters for economics. 4D says feature releases are delivered every three months and long-term support releases include fixes and library updates, while the maintenance program gives access to both release lines (https://us.4d.com/product-release-life-cycle). This creates a familiar subscription bargain: keep paying and stay current; stop paying and the application may still exist, but the upgrade and support path weakens. That bargain is rational for an application that runs critical workflow. It is painful for a buyer that feels it is paying just to stand still.
4D 21 LTS sharpens the argument. The 4D 21 page says the release is for applications designed to last and emphasises extending existing applications to the web, document reliability, identity and communication features, language maturity, connection reliability and data consistency (https://us.4d.com/new-4d-21lts). The wording is almost an admission of the customer problem: the product has to help old applications absorb new demands without asking customers to rewrite everything at once.
Price lists reveal a narrow but defensible paid unit
The U.S. price list gives the clearest public view of 4D's revenue logic. The January 1, 2026 U.S. PDF lists 4D Server including two users at USD 2,179 for a new purchase, USD 545 for maintenance and USD 1,639 for an upgrade from 20 to 21; client-expansion purchases are listed at USD 749 for one user, USD 3,779 for five users and USD 7,529 for ten users; web application and web services unlimited expansions are listed at USD 3,990 each; and subscriptions list 4D Server including two users at USD 50 per month, one additional user at USD 25 per month, and web application or web services expansions at USD 30 per month (https://download.4d.com/Documents/Website/PriceList/4D_Pricelist_USA.pdf).
These are not enterprise-suite prices in the Salesforce or SAP sense. They are small enough for a mid-sized customer or specialised software publisher to renew if the application keeps a real workflow alive. They are also large enough to matter if a customer has many users, multiple expansions, maintenance, partner fees, training and paid implementation labour. The price list says 4D Desktop with Write Pro and View Pro is USD 20 per month, while the partner program starts at USD 399 per year (https://download.4d.com/Documents/Website/PriceList/4D_Pricelist_USA.pdf). That shows a low entry point for development and a more modular bill as deployment expands.
The store page makes the same structure visible in a buyer-friendly format. It says a 4D Server subscription starts from USD 600 annually and lets two users connect through Windows, macOS, a web browser, a Qodly application or a mobile device, with the account tailored by adding clients as needed; 4D Desktop starts from USD 240 annually; partner programs are offered at Bronze, Silver, Gold and Platinum levels; and paid training sessions range from tens of dollars to several hundred dollars (https://store.4d.com/us/index.shtml). That is a service-continuity account, not a one-time disc sale.
The price logic depends heavily on customer context. For a two-user internal tool, USD 600 per year before developer time may be a cheap way to preserve a working application. For a large team needing web access, document features, expansion licences and external consulting, the same platform can become a meaningful operating commitment. A buyer should not compare only a headline monthly fee. It should price the entire account: server, users, expansions, maintenance, training, the local developer, testing, backups and the next upgrade.
The terms reinforce that subscriptions renew unless terminated and that the subscription is annual with a minimum of two users accessing the 4D application (https://us.4d.com/terms-and-conditions). They also say 4D may change prices once per calendar year during the term, and that a customer refusing a price revision may terminate the relevant service within a stated notice window. That creates a rational vendor lever: 4D can move pricing, but not without creating a moment when the buyer asks whether the application is still worth keeping.
The EULA adds another economic boundary. It defines maintenance as the update and upgrade service for 4D products and says clients may purchase licences and maintenance directly or through follow-on orders (https://us.4d.com/eula). Maintenance is not a decorative add-on. It is the buyer's path to corrections, enhancements and upgrades. When the application is important, maintenance becomes part of continuity insurance.
The pricing evidence does not tell us product margin. Software licence gross margin may be high, but support, product engineering, compatibility work, documentation, sales, partner management and training are real costs. The unit is likely attractive when renewal is steady and support burden is predictable. It becomes less attractive when older customer applications need expensive handholding, when upgrades break fragile custom work, or when the local channel has to spend too much time preserving systems that should have been rewritten.
Support labour is the product's hidden cost base
4D's professional-services page is explicit about the labour problem. It asks whether a customer has refused a project because of a deadline, needs more skilled people, cannot respond to an RFP because the required technology is outside the team's skill set, or is unsure whether an architecture will work securely once deployed; it then presents 4D Professional Services as help for those situations (https://us.4d.com/professional-services). That page turns the hidden cost base into a product feature. The buyer is not only buying software. It is renting access to people who know the platform.
The page also names database migration as a service area and says 4D can help customers get applications up to date while they concentrate on business (https://us.4d.com/professional-services). This is exactly where implementation memory becomes switching cost. A mature custom application is rarely a clean textbook case. It may have old forms, local naming conventions, custom reports, operating-system dependencies, printer habits, user workarounds and forgotten integrations. A migration is therefore both technical work and archaeology.
Training is another labour surface. 4D's training center says it offers sessions for beginner, advanced and expert levels, including on-demand training and customised training programs (https://us.4d.com/4d-training-center). The newer Learn 4D site presents categories for 4D database, language, Qodly Pro, web server, Write Pro, View Pro and related topics, with course counts and free learning materials (https://learn.4d.com/). Training lowers customer dependence on one local developer, but it also confirms that 4D is a specialised skill, not a commodity spreadsheet.
The technical-support page shows how responsibility is layered. It tells developers that they have multiple help options, and tells end users that the first point of contact should be the developer who created the solution (https://us.4d.com/4d-technical-support). This is economically sensible for 4D because the vendor cannot be the primary support desk for every custom workflow built by every partner. It also creates buyer risk. If the developer is weak, unavailable or adversarial, the end user's service experience can suffer even if the 4D product itself is functioning.
The general terms assign responsibility in a way that buyers should read closely. They say the customer is responsible for choosing and acquiring third-party hardware and software for use with 4D products, project management in multi-supplier IT systems, compliance with technical prerequisites, consequences of modifications made by the customer or its environment, and safekeeping of hardware, products, customer data, files, programs and databases during work carried out by 4D (https://us.4d.com/terms-and-conditions). In plain economics, 4D sells a platform and service path, but it does not absorb the buyer's whole operating risk.
The EULA also says 4D does not warrant that product functions will meet the client's requirements or that the application developed by the client will function correctly or meet objectives; it limits liability for many damages and caps liability in many cases at fees paid or payable over the preceding twelve months (https://us.4d.com/eula). This is normal software contracting, but it matters for pricing. The buyer cannot treat the renewal fee as full insurance against business interruption. The real insurance is design quality, backups, documentation, testing, trained staff and vendor or partner responsiveness.
That makes support quality a decisive but mostly private variable. Public pages prove that support and services exist. They do not prove queue times, seniority of responders, success rate for hard migrations, partner quality, customer satisfaction, or the number of engineers available in North America. A buyer renewing 4D should ask for support metrics and named escalation paths. An analyst cannot infer them from the public website.
Substitutes discipline the account from several directions
4D faces competition from several unlike substitutes, which is why a simple feature comparison misses the economics. Claris FileMaker is the closest buyer analogy: a custom-app platform with database, web and mobile surfaces, cloud or server hosting choices, and a partner ecosystem. Claris says its licensing includes FileMaker, Claris Connect and Claris Studio, and that buyers choose between FileMaker Cloud and FileMaker Server before choosing a tier (https://www.claris.com/pricing/). It also advertises monitoring, security, backups, REST API access, ODBC/JDBC and WebDirect, which puts direct pressure on any buyer considering 4D for small-team custom applications.
Microsoft Power Apps disciplines 4D differently. Power Apps Premium is publicly priced at USD 20 per user per month, paid yearly, with custom apps, Dataverse capacity, connectors, workflows and managed governance features (https://www.microsoft.com/en-us/power-platform/products/power-apps/pricing). Microsoft benefits from the installed Microsoft 365 base and broad developer familiarity. A customer already standardised on Microsoft can ask why it should keep a specialised 4D stack rather than build within Power Platform. 4D's answer has to be implementation memory, application depth, performance, ownership of an existing system, or a developer base that is already productive in 4D.
Mendix and OutSystems discipline the enterprise side. Mendix publishes a free tier, a Basic tier starting around EUR 50 per month depending on plan, Standard starting at higher monthly prices, and support or uptime differences across tiers (https://www.mendix.com/pricing/). OutSystems says its Developer Cloud pricing is custom-quoted, with professional support, OutSystems Cloud, self-hosted options, a 99.5 percent uptime guarantee and higher guarantees available as add-ons (https://www.outsystems.com/pricing-and-editions). These products are not direct replacements for every 4D application, but they teach buyers to expect cloud-native deployment stories, broad integration programs and enterprise support choices.
The in-house team is another substitute. A company with strong developers can rebuild an old 4D workflow on PostgreSQL, SQL Server, a web framework and a cloud provider. That may reduce licence dependence and widen hiring options. It may also cost far more than the renewal if the existing workflow is complex. The key economic question is whether the buyer has enough internal capacity to carry requirements discovery, data migration, test automation, user training and support after launch. Many small and mid-sized buyers do not.
A larger integrator is a substitute too. The integrator may recommend a packaged ERP, CRM, inventory system or industry SaaS platform. That route can reduce dependence on a narrow 4D skill base, but it also introduces consulting fees, scope creep, long deployments and new vendor lock-in. It is not automatically cheaper. It becomes attractive when the old 4D application is blocking growth, compliance, reporting or integration with modern systems.
Delayed automation is the cheapest substitute in the short run. A buyer can defer a rewrite, keep a spreadsheet next to the old application, and ask staff to work around the gaps. That choice is common because it does not need budget approval. It is also costly when manual exceptions pile up. 4D's renewal appeal improves when the alternative is operational drift rather than a clean replacement.
These substitutes explain why 4D's pricing can survive despite older technology perception. The buyer is not choosing in an abstract software lab. It is choosing under constraints: who knows the current application, who can fix it this month, how much business data is inside it, how many users will resist change, and how much downtime the company can tolerate.
The handover is where the account becomes expensive
The implementation handover is the most revealing commercial moment because it exposes whether the customer owns a system or merely depends on someone else's memory. A clean 4D account has clear data dictionaries, documented user roles, tested backup and restore procedures, named licence owners, a known version path, written integration notes, current operating-system support and at least two people who understand the application. A weak account has one retired developer, a folder of partial notes, old server habits, custom reports that no one wants to touch and users who know only that "the old screen works." The same 4D invoice means different things in those two cases.
That difference explains why renewal value cannot be inferred from the price list alone. A USD 600 annual server subscription can be either a bargain or a trap. It is a bargain when it preserves an application that would cost six figures to rediscover and rebuild. It is a trap when the payment lets management postpone documentation, upgrade planning and staff training. The economics are not in the licence line. They are in the work the buyer has or has not done around the licence.
4D's own service language recognises this. The professional-services page asks whether the buyer needs more skilled people, faces a deadline or is unsure whether a solution architecture will work securely once deployed (https://us.4d.com/professional-services). Those are not fringe cases. They are the day-to-day reasons specialist software accounts persist. A buyer does not renew only because the software has features. It renews because someone has to keep an operational process alive while staff, rules, customers and technology change around it.
The handover also exposes a common measurement error. Management often asks whether the software is old. That is not the decisive question. An old system can be economically healthy if it is documented, backed up, patched, well understood and still fits the workflow. A newer platform can be economically weak if the team cannot implement it, users reject it, integrations are fragile, or reporting gaps force manual work. 4D should be judged against the customer's total operating alternative, not against the fashion cycle of development tools.
The local-support element matters here. 4D Inc.'s U.S. presence gives North American buyers a local sales and support route, while the wider group supplies product releases and documentation (https://us.4d.com/4d-around-the-world). But the practical handover often happens between a customer and a local developer, not directly with the platform vendor. If that developer has built a maintainable application, 4D's narrow ecosystem can be efficient. If that developer has made the application opaque, the same narrow ecosystem raises the buyer's cost of escape.
This is why customer dependence should not be framed only as vendor lock-in. Some dependence is productive. A law office, clinic, school or distributor may rationally depend on a custom application because it captures workflows that generic software cannot. The problem begins when dependence is undocumented, concentrated in one person and untested under failure. 4D benefits from accumulated implementation memory, but the buyer benefits only when that memory is transferable.
The facts a buyer should demand are therefore operational rather than rhetorical. How long would it take a new developer to make a safe change? Are the licence records current? Can the application be restored from backup on a clean machine? Which reports are business-critical? Which external systems exchange data with it? Which users have administrative rights? Which version is in use, and what is the supported upgrade path? Those answers decide whether the renewal is a continuity purchase or a delay purchase.
Public evidence cannot answer those questions for 4D's customer base. The official pages prove that 4D sells the surrounding platform, maintenance, training and support surfaces. They do not show the quality distribution of deployed applications. A strong public article therefore has to keep the inference modest: 4D's economic opportunity is the handover pain in specialist business systems; the public record does not prove how often that pain creates satisfied renewals rather than reluctant lock-in.
The customer base is likely mixed between new work and preservation work
4D's public story wants to be read as active development, not only preservation. The current homepage highlights 4D 21 LTS, recent webinars, free training content, web extension, document tools, mobile and developer resources (https://us.4d.com/). The GitHub organisation shows public repositories updated in 2026, including components for mobile app server, Write Pro interface, widgets, View Pro, NetKit and other tools (https://github.com/4d). These signals are consistent with an active product group.
At the same time, the strongest economics may come from preservation. A product launched in the 1980s and still used in specialist workflows will naturally have older applications whose replacement cost is high. 4D's own 4D 21 LTS page speaks to applications designed to last and argues that existing teams, architecture and delivery models can be kept while features expand (https://us.4d.com/new-4d-21lts). That message is aimed at continuity buyers. It says, in effect, that the customer can modernise without losing what already works.
The distinction matters for valuation of the account. New-project demand is healthier because it shows customers still choose 4D against current alternatives. Preservation demand can also be profitable, but it is more vulnerable to demographic and skills pressure. If the product base depends heavily on ageing applications and ageing developers, revenue can remain stable for years before weakening. If the company can turn those customers into renewed, web-enabled, trained and documented accounts, the installed base becomes a platform for further work.
The public sources do not show the split. Store prices, training pages, product releases and GitHub updates show supply. Customer references and reviews show selective demand. They do not reveal how much revenue comes from new development, upgrades, maintenance on old systems, partner programs, professional services or training. That missing split is one of the largest evidence limits in judging 4D INC.
There is a practical way to think about it. A buyer starting from zero compares 4D with Claris, Power Apps, Mendix, OutSystems, a web framework and packaged SaaS. A buyer with a functioning 4D application compares renewal with disruption. These are different sales. The first sale has to win against market alternatives on features, labour availability and confidence. The second sale has to prove that the existing application remains worth preserving and extending.
The second sale is easier to close but harder to keep honest. Users already know the system. Data is already in it. Reports are already trusted. The developer already knows the workarounds. Finance sees a smaller annual invoice than a rebuild proposal. Those facts create switching resistance. But if the buyer never tests recovery, documents logic, cross-trains staff or plans upgrades, the account silently accumulates debt. The service looks cheap until something breaks.
This is where 4D's training and support investments become economically important. Free or paid training, partner programs and professional services can convert preservation demand into maintainable continuity. A buyer that renews and sends staff through training is buying future optionality. A buyer that renews and does nothing is buying another year of dependence. The vendor benefits from both in the short run, but only the first pattern supports a durable reputation.
For 4D INC, the most valuable North American customers are probably those that use 4D as a living application platform rather than a frozen legacy system. Public evidence supports the possibility of that living use through current releases, store offerings, learning resources and public repositories. It does not prove the proportion. That is why the article treats implementation memory as the thesis but keeps the judgement conditional.
The buyer should price exit even when it plans to stay
A disciplined renewal should include an exit price. This does not mean the buyer should leave. It means the buyer should know what leaving would cost. Without that number, renewal can look artificially cheap. With that number, 4D's value can be judged more fairly.
The exit price has several parts. Data extraction is first: tables, files, attachments, reports, user permissions, historical records and audit needs. Process discovery is second: which screens represent real work, which steps are habit, which rules are legal obligations and which reports drive management decisions. Technical replacement is third: a new database, application layer, hosting choice, authentication, backups, reporting, document output and integrations. Organisational change is fourth: training, testing, parallel running, support desk load and the cost of errors during migration.
4D can be rational if that exit price is high and the current system is stable. It can be irrational if the exit price is high only because nobody understands the current system. Those are different forms of switching cost. The first is valuable accumulated knowledge. The second is neglected maintenance. Public evidence cannot distinguish them for the customer base, but a buyer can distinguish them internally.
The EULA's warranty and liability language makes this discipline even more important. 4D does not promise that a customer-built application will meet the customer's goals, and the customer bears responsibility for protecting its data (https://us.4d.com/eula). That is not unusual, but it means the buyer must own the continuity plan. Renewal cannot substitute for governance.
The same logic applies to cloud and hosting choices. 4D's website and account surfaces use external infrastructure providers, and the legal notice names OVH for website hosting (https://us.4d.com/legal-notices). But a customer's application may be hosted elsewhere, including customer-managed or partner-managed environments. The buyer should document who controls hosting, backups, administrative credentials, updates and incident response. If the answer is "the developer handles it," the buyer has not priced exit.
Exit pricing also clarifies the role of substitutes. Power Apps may be cheaper on a visible per-user basis, but only after the buyer maps the old workflow into Dataverse, connectors and governance. Claris may feel more familiar for custom apps, but migration still requires data and process work. Mendix or OutSystems may bring stronger enterprise support, but often with custom quotes and project scope. A packaged SaaS product may remove custom maintenance, but only if it actually fits the workflow. The substitute that wins in a spreadsheet may not win in a migration room.
For 4D INC, this exit discipline is both a threat and an opportunity. It is a threat because a buyer that maps the system carefully may discover a cleaner replacement path. It is an opportunity because the same mapping may reveal that 4D remains the lowest-risk option if paired with documentation, upgrades and training. The vendor should prefer that second outcome because it turns reluctant renewal into defensible continuity.
The public article cannot see whether 4D's customers are doing this work. It can only state the economic standard. A healthy 4D renewal should reduce future switching panic, not deepen it. The customer should emerge from renewal with clearer documentation, a known upgrade path, named support contacts and a realistic migration estimate. If the renewal only preserves opacity, the account's apparent value is overstated.
Customer evidence shows breadth, not audited demand
4D's references page presents customer stories across sectors and countries, with filters for industries such as education, healthcare, government, legal, logistics, manufacturing, media, non-profits and professional services (https://us.4d.com/references). The page is curated by 4D, so it cannot be treated as a representative customer sample. It does, however, show the range of workflows for which the company wants to be considered: not a single vertical product, but a platform for many bespoke operational systems.
The homepage also displays a "They use 4D" section and routes readers to references (https://us.4d.com/). Because these are vendor-presented logos and stories, the right inference is limited. They show commercial positioning and possible use cases. They do not prove active contracts, current revenue, renewal rate or satisfaction across the base. The better question is whether the referenced use cases share a common economic pattern. They do: each suggests a customer that preferred a tailored application over a fully packaged system.
That pattern is 4D's defensible niche. In a small or mid-sized enterprise, the most valuable software may be a custom tool that fits local process better than a generic SaaS product. 4D can be attractive when the workflow is too idiosyncratic for a standard package but too small for a large custom engineering program. The company does not need to win against every modern platform. It needs enough customers whose existing or planned workflows justify a specialised account.
But customer breadth also creates support variance. A platform serving education, healthcare, manufacturing, government and professional-services workflows faces very different data sensitivity, reporting, uptime, regulatory and integration demands. A vendor can publish general platform features, but implementation quality depends heavily on the developer and the customer's own governance. This is why the technical-support page's instruction to contact the application developer first is not a minor note. It is the operating model.
The public review signal is thin and mixed. G2 lists 4D with a 3.3 out of 5 rating from two reviews, both from small businesses, and says there are not enough reviews to provide buying insight (https://www.g2.com/products/4d/reviews). One review praises customisation and data capacity while warning about siloed data and third-party support problems; another praises sales-data capacity while saying the software feels old and could be easier to use. These are anecdotes, not a statistically useful sample. They are still useful because they echo the core tradeoff: capacity and custom fit on one side, labour dependence and ageing user experience on the other.
The developer signal is also narrow but active. GitHub verifies that the 4d organization controls the 4d.com domain, shows 86 followers, links to official documentation, the blog, the forum, 4D Depot and the mobile organization, and lists 55 public repositories, including components for builds, plug-ins, NetKit, SQL libraries, Write Pro interface, mobile app server, View Pro, SVG and AIKit (https://github.com/4d). Many repository star counts are modest. That does not prove low commercial usage, because customers of a proprietary development platform may not star public repositories. It does show that the public open-code ecosystem is not a mass-market developer flywheel on the scale of major open-source stacks.
DB-Engines provides an independent database-market context. Its 4D system page describes 4D as an application development environment with integrated database management, developed by 4D Inc., with initial release in 1984, commercial or open-source-commercial licensing, macOS and Windows server operating systems, SQL support, ODBC, RESTful HTTP API, SOAP web services, stored procedures, triggers, multi-source replication, ACID transaction concepts, concurrency and users/groups access control (https://db-engines.com/en/system/4D). Its July 2026 ranking lists 434 systems and places 4D at rank 122 with a score just above 2, far below mass-market relational systems (https://db-engines.com/en/ranking). That is not a defect by itself. It confirms that 4D is a specialist product in a crowded market.
The market-signal conclusion is therefore cautious. Public chatter supports the idea that 4D is durable, specialised and not mainstream. It does not support claims of broad developer momentum, current customer growth or superior satisfaction. The economic case has to rest on installed-base continuity and customer-specific switching cost, not on visible market buzz.
Resource evidence points to supplier dependence, not network ownership
Network and hosting evidence should be kept in its lane. Public DNS observed on July 8, 2026 returned 135.125.246.26 for 4d.com, while us.4d.com resolved through fr.4d.com to the same address. The 4d.com nameservers were Amazon Route 53 nameservers: ns-935.awsdns-52.net, ns-99.awsdns-12.com, ns-1420.awsdns-49.org and ns-1901.awsdns-45.co.uk. The store resolved to 194.177.35.87, developer.4d.com to 57.128.215.27, and account.4d.com to 149.202.49.50. Reverse DNS returned a Waycom customer hostname for the store address, OVH VPS hostnames for the developer and account addresses, and no reverse name for the main 4d.com address.
WHOIS queries add a bounded registry view. The 135.125.246.26 address sits in a RIPE assignment named PCI-DE1 under OVH GmbH with route origin AS16276; 194.177.35.87 sits in a RIPE assignment named WAYCOM-FR-4D, described as customer servers, with Waycom International SAS and route origins including AS30889; 57.128.215.27 sits in OVH Poland VPS space with route origin AS16276; and 149.202.49.50 sits in an OVH SAS allocation in France with route origin AS16276. These are point-in-time public records, not a map of the product's full architecture.
4D's legal notice aligns with part of that picture. The website legal notice says the website is published by 4D SAS and hosted by OVH SAS in Roubaix, France (https://us.4d.com/legal-notices). That is evidence of supplier use. It is not evidence that 4D Inc. owns data centers, autonomous systems, customer production infrastructure or every public service endpoint.
The privacy policy adds a data-processing lens. It says 4D collects personal data for purposes including account management, marketing, website personalisation, quality control, fraud prevention, legal obligations and business reorganisation scenarios (https://us.4d.com/privacy-policy). It does not provide a complete subprocessor list for every customer application. The public buyer should therefore separate website data handling from customer application deployment. A 4D application may run on a customer's own server, a partner-managed environment, a cloud instance or another arrangement. Public DNS for 4d.com does not prove where a customer's operational data lives.
This distinction matters because the assigned category includes cloud service. 4D sells cloud-adjacent and web-enabled capability, and its store, documentation, account portal, learning platform and website are online services. But the product is not presented as only a database-as-a-service. DB-Engines explicitly says 4D is not cloud-based only (https://db-engines.com/en/system/4D). The resource story is therefore hybrid: official web surfaces use external infrastructure providers, while customer applications can be deployed in different environments depending on licence, partner, customer choice and technical design.
Supplier dependence is not inherently negative. A private software group would be inefficient if it tried to own every hosting, DNS and network asset. The buyer's real diligence questions are practical: where is my production application hosted, who manages backups, what happens if the hosting provider has an incident, who has access to logs, which party is responsible for security updates, how are licences activated, and how quickly can the application be moved if a supplier becomes unacceptable?
The terms push some of that responsibility back to the customer. They say the customer is responsible for third-party hardware and software, multi-supplier project management and compliance with technical prerequisites (https://us.4d.com/terms-and-conditions). That makes sense if many applications are customer-hosted or partner-managed. It also means a buyer should not treat 4D's public hosting choices as the whole service-continuity story. The account's reliability lives in the combination of 4D product quality, the application developer, the hosting operator, customer governance and backup discipline.
Regulation and geopolitics sit mostly in customer deployment
4D's legal and regulatory posture is mostly French and contractual at the group level, with a U.S. commercial office for the assigned entity. The legal notices identify 4D SAS, registered in France with a Versailles registration number and French VAT number, as website publisher (https://us.4d.com/legal-notices). The EULA says French law governs the agreement and disputes are subject to courts in Versailles (https://us.4d.com/eula). A U.S. buyer working through 4D Inc. should understand whether its own order, support arrangement and data processing terms are with the U.S. company, the French parent, a reseller, a partner or another contracting party.
The geopolitical issue is not sanctions drama or public procurement exclusion; public evidence does not support that kind of claim. The issue is contract clarity and operational jurisdiction. A North American customer may have data residency, privacy, education, healthcare, public-sector or client confidentiality obligations. 4D can be used in many such contexts, but compliance depends on how the customer application is built and hosted. The vendor's general platform claims cannot prove a specific customer's compliance.
This is especially important for older custom systems. A business application that began as a local database may now hold personal data, medical scheduling details, student records, payment workflows, inventory traceability or employee information. The original developer may not have designed it for current privacy, retention or audit expectations. 4D's product updates can help, but they do not automatically fix governance gaps inside a customer's own application.
The EULA's risk allocation should be read with that in mind. It says the client bears the risk of choosing and using the products and the results obtained, including application development, and that the client is responsible for protecting its data (https://us.4d.com/eula). That allocation is commercially normal, but it means renewal is not enough. A buyer renewing 4D for a sensitive workflow also needs a data audit, access review, backup test, disaster-recovery plan and documentation of who can support the application if the primary developer leaves.
Operational risk also comes from platform lifecycle. 4D supports both feature releases and long-term support releases, but old customer applications may sit several versions behind. The product-release page says the maintenance program gives access to both release lines and invites customers to contact sales for help selecting a release (https://us.4d.com/product-release-life-cycle). The economic question is whether the buyer can upgrade steadily or whether it has deferred maintenance until the application has become expensive to move.
This is where 4D's continuity pitch can become either valuable or dangerous. If 4D and its partners help customers keep applications current, renewal preserves optionality. If customers use renewal only to postpone hard decisions, switching cost grows while resilience falls. The difference is private and customer-specific.
The judgement turns on facts that are not public
The bullish case for 4D INC is straightforward. There is a durable installed base of custom business applications. The product group has been operating for decades, publishes a current 2026 price list, offers a U.S. office and support path, keeps training and learning resources alive, releases new product versions, and maintains public developer resources. For a small or mid-sized buyer with a working 4D application, renewing can be much cheaper and less risky than a rebuild.
The bearish case is equally clear. The visible developer ecosystem is narrow, public review volume is tiny, mainstream database rankings place 4D far below broad-market systems, and buyers may struggle to find available developers compared with Microsoft, web, SQL or low-code alternatives. The support model depends heavily on the application developer or partner. If the local developer disappears, implementation memory can turn from an asset into a hostage situation.
The facts that would most change the assessment are private operating facts. Renewal rate would tell whether customers stay because they are satisfied or merely stuck. Churn after major upgrades would show whether the release path protects customers. Support response time and escalation outcomes would reveal whether the labour product is strong. Partner concentration would show whether the North American account depends on a few critical specialists. Paid seat count and revenue by product line would clarify whether 4D Server, desktop, expansions, partner programs, training or services carry the economics.
Customer-side facts would matter just as much. How many critical applications have current documentation? How many customers test backups? How many have more than one developer who can maintain the application? How many applications are still on unsupported operating systems? How often does a customer choose 4D for a new project rather than only for continuation of old systems? Public sources cannot answer these questions, and the article should not pretend otherwise.
The investment-style conclusion is therefore narrow. 4D INC matters where the paid account is an economical preservation and extension of a useful custom application. It matters less where the buyer is starting from a clean sheet and can choose a mainstream cloud platform, packaged SaaS system or larger developer pool. The company's public evidence supports a specialist continuity business, not a broad claim of market dominance.
That is why the opening renewal call is the right lens. The service is not the name on the software. It is the accumulated configuration memory, the support labour, the partner knowledge, the upgrade path, the backup routine, the reports users still trust and the migration avoided for another year. If those pieces are healthy, 4D can be rational even in a market full of newer alternatives. If they are weak, the same switching cost becomes a warning sign, and the buyer should spend the renewal conversation planning an orderly exit rather than another year of delay.