BareMetal.com Inc and the infrastructure economy that refuses to disappear
BareMetal.com Inc is not important because it is a hyperscale cloud provider. It is important because it is the opposite type of infrastructure company: small, old, operationally specific, hard to classify, and commercially revealing. Its public record shows a Canadian hosting and domain registration operator that started in the mid-1990s, incorporated in 2000, served long-tail web customers and domains, relied on upstream data center and network providers, and ultimately sold the valuable BareMetal.com domain while continuing under BareMetal.ca. This sequence is a compact case study of the dedicated infrastructure economy after the first era of web hosting.
The central conclusion is that BareMetal.com Inc illustrates how the hosting economy is shaped less by visible brand scale than by rare operational assets: IPv4 address allocations, registrar accreditations, DNS control, customer billing relationships, long-duration web workloads, upstream data center access, and accumulated trust. The company name became a market category. “Bare metal” now refers to dedicated physical servers consumed with cloud-like APIs, but BareMetal.com Inc’s public pages describe a broader web hosting and domain registration business in Canada, whose durability comes from support, continuity, and low churn rather than a venture-scale cloud platform. Its sale of the.com to a successor context linked to i3D.net crystallizes the business argument: the old host survived, but the most liquid asset became the category-defining domain.
There is also an evidentiary correction. The directory line index identifies the target as BareMetal.com Inc, but the ASN 138282 index in delegated statistics does not publicly correspond to BareMetal.com Inc. Public records derived from APNIC identify AS138282 as DMRC-AS, associated with Delhi Metro Rail Corporation Limited in India, and not with BareMetal.com Inc. The commercially relevant network trail for BareMetal.com Inc is instead the ARIN entity BAREM-2 and a reassigned /24 IPv4 subnet, 67.223.102.0/24, inside the larger 67.223.96.0/20 block from Priority Colo and the AS30176 routing environment. This distinction is important because it changes the economic interpretation of the company: BareMetal appears not as an autonomous network owner, but as a hosting and registrar operator dependent on a specialized colocation and network provider.
The company behind the name
BareMetal's official history describes a company born from consulting work around Internet connectivity and UNIX support, then shifting to web and hosting services in 1995. The company says its first customers were friends and bases its operational ethic on treating customers like friends. The sole proprietorship was converted to BareMetal.com Inc in 2000. This coincides with the Better Business Bureau profile, which shows the start of business and incorporation date as June 29, 2000, identifies the legal form as a corporation, lists BareMetal.com Inc as an alternate name, and designates Tom Brown as owner; BBB also notes that it does not verify all third-party information, so its management information should be treated as secondary evidence rather than an official company registry.
The company's current public presence has shifted from the.com to the.ca domain. BareMetal.ca states that the company is a Canadian web hosting and domain registration specialist “since 1995.” More unusually, it also states that as of May 2026, the company has “virtually completed” the transition from BareMetal.com to BareMetal.ca, that it is “100% Canadian owned, staffed, and physically present,” and that “the.com was sold,” with the sale proceeds to “repay some debts.” This single sentence is unusually information-rich. It confirms the continuity of the operating company, the separation between the company and the top-level domain asset, the Canadian operational identity, and a financial motivation for asset sale rather than a simple rebrand.
The name itself predates the modern “bare-metal cloud” market. BareMetal's “About” page traces the expression to the Hacker Jargon File and says it refers to working “at the hardware level” and building systems from scratch. The company interprets the name as implying depth, clean systems, and attention to detail. In the 1990s, this was a credibility signal for technical web hosting: the provider understood UNIX, servers, connectivity, and hands-on infrastructure. In the 2020s, the same phrase became a product category for dedicated physical servers consumed as cloud infrastructure. This semantic shift is at the core of the company's business story.
The evidence does not support treating BareMetal.com Inc as a modern bare-metal cloud operator in the same sense as i3D.net, OVHcloud, the former Equinix Metal category, or automated dedicated-server platforms. BareMetal's product pages emphasize web hosting, virtual servers, secure web services, domain registration, DNS, email services, SQL databases, logs, and related hosting features. Its business promise is not “metal provisioned by global API,” but support, affordability, registrar services, and continuity. This makes the company more analytically useful, not less. It is a case of survival from the first era of hosting, when customers bought websites, domains, email, CGI/PHP/MySQL-type hosting, and trust in a small operator, not elastic compute primitives.
A business model built from small frictions
BareMetal's web services page states that the company specializes in web hosting, customer service, and affordability, explicitly contrasting its approach with “easy, quick profit.” It lists virtual servers, domain registration, secure web services, redundant servers, virtual FTP, mailing lists, SQL databases, logs, and related services. It also states that its pricing structure is competitive, tiered pricing is available, and surcharges only apply to very high-traffic sites. This is a classic long-tail hosting model: low average revenue per account, low-touch infrastructure, retention heavily dependent on support, and profitability reliant on grouping many small customers onto shared systems while avoiding catastrophic support load.
The domain registration piece adds a second revenue layer. BareMetal says it has been a CIRA-certified.ca registrar since 2000 and an OpenSRS reseller for other domains since 1999 or 2000. It offers.CA,.US,.COM,.NET,.ORG,.INFO, and.BIZ registration, with optional DNS, web forwarding, parking, mail forwarding, and related domain services. CIRA’s registrar model places registrars between domain name holders and the.CA registry, meaning the business relationship belongs to the registrar even though the registry controls the authoritative zone. BareMetal’s domain page also emphasizes TBR.CA, or drop-catching/backorder participation, which indicates a niche clientele beyond ordinary small-business hosting: domain investors, Canadian holders, and customers who value a registrar with operational knowledge of expiration cycles.
This bundling has economic significance. A customer whose domain is registered via BareMetal, DNS hosted by BareMetal, web hosting on BareMetal, mail forwarding or email services configured via BareMetal, and billing records in the BareMetal customer portal, faces more than a simple price comparison when considering migration. Moving the account requires domain transfer authorization, DNS zone export or reconstruction, MX and SPF/DKIM/DMARC record verification, web content transfer, and import, SSL changes, mail migration, cron/script compatibility checks, and a billing switch. None of these frictions are insurmountable, but together they create inertia. For a small business, club, charity, heritage content site, or owner-managed domain portfolio, the rational decision may be to keep paying a familiar provider even if a cheaper commodity host exists.
BareMetal’s terms allocate operational responsibility in a hosting-typical way. Customers must maintain accurate contact information and are responsible for backups and acceptable use. BareMetal reserves the right to immediate termination for security, stability, or integrity reasons. Service credit provisions are narrow: outage credits are subject to exceptions and depend on BareMetal’s equipment or error being the direct cause. The registration agreement also contains liability limitations, including a clause that BareMetal is not liable for substitute services and limits certain liabilities to $500. The business implication is clear: the provider sells continuity and support, but does not guarantee the full economic value of the customer’s website, domain, email archives, or business interruption risk.
This is one reason why old hosting relationships persist. The customer is formally responsible for their own backups, security choices, and account information, but informally depends on the host’s institutional memory. The host may know which customers have old scripts, which zones are fragile, which mail forwarders are still in use, which billing contacts are obsolete, and which domains are business-critical. This knowledge is not visible on a balance sheet, but it is operational capital. It also has an asymmetric value profile: it is worth little to outsiders until something breaks, and then it can be decisive.
The low public footprint is itself evidence
BareMetal.com Inc does not have the public footprint of a high-growth infrastructure company. There is no visible investor relations presence, no hyperscale data center map, no listing on a public cloud marketplace, no large management team on the public web, and no dense stream of engineering job postings found in ordinary public archives. Instead, the footprint consists of official company pages, registrar records, hosting terms, an account portal, WHOIS/RDAP traces, customer and forum traces, and third-party hosting directories.
This absence should not be interpreted as failure. In the infrastructure economy, opacity often reflects the type of business. A small hosting operator that is profitable or nearly profitable can exist for decades without press releases. Its market is not the public narrative; it is renewals. Its central question is not whether it can win new enterprise contracts against Amazon Web Services or Microsoft Azure. It is whether enough customers keep renewing their domains and hosting plans, whether servers stay up-to-date and paid for, whether upstream providers remain stable, and whether support load remains below the contribution margin of the account base.
Public reputation traces are sparse. The BBB profile shows no customer reviews or complaints on the pages consulted, but this proves neither quality nor scale; it is simply evidence that this channel has not accumulated visible disputes. A domain forum profile identifies a BareMetal.com service representative active in Canadian domain discussions, and forum discussions show that BareMetal is mentioned by users as a Canadian hosting or registrar option. These are unofficial traces, but commercially they suggest a company that has remained visible in the Canadian domain community even as the broader hosting market consolidated.
Hosting review traces are also thin and must be weighted with caution. One hosting review listing described BareMetal.com as offering shared hosting and domain registration, with an old review referencing “cloud” and “bare-metal” language, but the sample is too small to infer customer satisfaction or revenue. A NamePros forum thread contains user comments about BareMetal as a registrar/host, but again this is anecdotal. The information gain is not statistical; it is categorical. BareMetal existed in the collective memory of domain and hosting users, not just in official company pages.
Address resources and the scarcity premium
The most concrete infrastructure evidence is the IP allocation. Public records derived from ARIN identify 67.223.102.0/24 as a reassigned network block for BareMetal.com Inc, with org ID BAREM-2 and an address in Victoria, British Columbia. The parent block is 67.223.96.0/20 from Priority Colo. Third-party IPinfo records identify hostnames such as redir.baremetal.ca in this range and show the wider 67.223.96.0/20 route originates from AS30176, Priority Colo. RPKI status is reported as valid for the routed aggregate.
Commercially, this is a different profile from a company that owns and originates its own portable IP space. A reassigned /24 gives BareMetal operational addressing capacity, but routing, RPKI, and upstream dependencies appear tied to Priority Colo’s network. This reduces the operating burden of an autonomous system, transit contract maintenance, and global routing policy management. It also reduces strategic autonomy. If BareMetal wishes to move the entire service stack to another facility or network, address portability may be limited both contractually and by the fact that the public route is Priority Colo’s aggregate, not necessarily BareMetal’s own independently originated prefix.
IPv4 scarcity changes the economics even of small hosting businesses. A /24 holds 256 addresses, fewer after network, gateway, broadcast, or operational reservations. In a shared hosting model, many domains can hide behind a single IPv4 address using name-based virtual hosting. In the early SSL era, dedicated IP addresses were often required for separate certificates; Server Name Indication (SNI) reduced this pressure, but not all legacy stacks or customer assumptions have disappeared. Mail reputation, custom DNS, reverse DNS, reseller isolation, abuse containment, and customer expectations can still create demand for distinct addresses. A provider with its own historically used block has an asset-like operational advantage, even if it does not own the block in the capital-market transferable sense.
Address scarcity also affects customer discipline. Dedicated hosting customers tend to request static addresses, reverse DNS, separate test environments, VPN endpoints, monitoring addresses, and sometimes multiple IPs for technically weak but commercially familiar reasons. The provider must ration. Each additional IP address for a customer has an opportunity cost. In the post-exhaustion IPv4 world, the address pool is no longer an incidental technical input; it is a limiting factor for product design and abuse risk.
The AS138282 index is important because it shows how easy it is to misinterpret infrastructure evidence. Public records derived from APNIC place AS138282 at Delhi Metro Rail Corporation Limited in India. If one mechanically matched the directory line to the delegated AS number, one would infer a nonexistent BareMetal autonomous network in Asia. The correct economic conclusion is the opposite: the visible trail of BareMetal’s address resources points to a Canadian hosting operator using reassigned space under Priority Colo. This misdirection reinforces the case for entity-level reconciliation across RIR, RDAP, routing, and company evidence before drawing business conclusions.
Data center dependency and the Toronto anchor
BareMetal’s business and support identity is Canadian and Victoria-based, but the infrastructure trail points to Priority Colo and Toronto network infrastructure. Priority Colo describes itself as offering colocation, dedicated servers, and related services on redundant infrastructure, with operations in Greater Toronto Area facilities since 2002. Its public materials emphasize a small team, colocation, data center economics, network administration experience, and economies of scale.
Priority Colo’s network page describes relevant data center inputs: HVAC, fire systems, floor loading, security, multiple paths, transit, and transport. It lists a BGP mix including Tata Communications, Level 3, TiNET, Cogeco Data Services, and TorIX, with additional transit via Zayo. It also references redundant layer-2 paths to 151 Front Street and an in-building meet-me room ecosystem with over 150 operators. PeeringDB identifies Priority Colo as AS30176, with North American traffic, an open peering policy, IPv4 and IPv6 prefix counts, and public peering details. BGP.tools lists AS30176 as an ARIN-allocated network registered in 2003, with upstreams including Lumen, Tata, and Hurricane Electric, and shows 67.223.96.0/20 among valid originated IPv4 space.
This provider relationship is economically rational. A small host does not need to own a data center to sell hosting. It needs reliable rack space, remote hands, power, cooling, IP transit, anti-DDoS posture, routing competence, and emergency response. Buying these inputs from a colocation/network specialist converts fixed capital expenditure into a recurring provider cost. This allows the hosting company to focus on customer accounts, registrar operations, server administration, and support. But it also creates dependency. If the upstream facility, routing provider, or data center contract changes, customer service continuity is exposed.
Toronto is a natural anchoring point for such a Canadian operator. 151 Front Street West is one of Canada’s premier carrier hotel locations, and the Cologix TOR1 facility page on PeeringDB lists the 151 Front Street address and a dense exchange ecosystem, including TorIX. Priority Colo is among the networks present in that facility. For a Victoria-based company serving Canadian and international web customers, this topology makes sense: business administration and support can be on Vancouver Island, while servers sit near dense interconnection in Toronto.
The separation between headquarters and server location is not a footnote. It is the business model. Infrastructure companies arbitrage geography. The customer may buy “Canadian hosting” from a Victoria company, while the packets flow through Toronto, transit providers, and exchange fabrics. Legal comfort, the support relationship, and the customer’s currency can be local; the efficient physical location of the infrastructure can be where power, cooling, and network density are best.
Dedicated server offering and the old hosting cost curve
Bare-metal hosting, in the modern literal sense, means a physical server dedicated to a single tenant. OVHcloud and other providers describe bare metal as single-tenant physical infrastructure leased to customers without the virtualization layer that characterizes much of cloud computing. i3D.net’s current bare-metal cloud page states that customers run directly on dedicated servers with no hypervisor and no noisy neighbors, while consuming capacity via cloud-like tools such as APIs, Terraform, BMC access, and on-demand or committed models.
The economics are simple but ruthless. A dedicated server has a high fixed cost and non-modular capacity. The provider buys or leases hardware, installs it, powers it, cools it, monitors it, connects it, replaces failing drives, handles abuse, and eventually retires or redeploys the asset. Unlike a virtualized cloud node, a dedicated machine cannot be efficiently carved up among many unrelated tenants unless the provider itself becomes a virtualization provider. If a customer leaves after three months, the provider may end up with stranded hardware configured for a workload that no longer exists. If the customer stays for years, the server can become highly profitable after capital recovery, provided power, support, and failure rates remain controlled.
This is why old hosting companies often prefer simple products and long customer lifetimes. A shared hosting server can support many low-traffic sites. A domain registration account can renew for years with minimal intervention. DNS, mail forwarding, and parking services are lightweight. The economics improve when the provider avoids custom enterprise obligations, aggressive service-level penalties, and high-touch migrations. A small host can survive by being boring: stable pricing, stable name servers, stable support, and few forced platform changes.
The same mechanisms explain the modern bare-metal cloud market. The customer wants physical isolation, predictable performance, direct hardware access, and network quality. The provider wants committed capacity so hardware is not stranded. i3D’s page makes this explicit by distinguishing committed capacity from on-demand hourly use. It states that committed bare-metal capacity equates to traditional dedicated bare metal for predictable long-term workloads, while on-demand servers support rapid deployment and burst usage. It also states that each server includes a public IPv4 address, a traffic allowance, redundant uplink, and a premium network. The inclusion of a single IPv4 address is not incidental; it is an economic signal about address scarcity.
BareMetal.com Inc’s public footprint sits on the older side of this curve. Its pages do not present an automated global dedicated-server fabric. They present a hosting and registrar operator with long-duration services. But the business mechanisms are in continuity with the modern market. Physical servers are capital goods. IP addresses are scarce. Customer migrations are risky. Data centers are specialized providers. Network quality is bought via upstream relationships. Support and trust determine retention. The difference is scale and packaging.
Customer lock-in without monopoly power
The apparent customer lock-in at BareMetal is not monopolistic lock-in. Customers can transfer domains, change DNS, move websites, and change email providers. The lock-in is procedural and risk-based. The smaller and older the customer, the greater the friction.
A domain may be the login identifier for a bank account, a government portal, a nonprofit donation system, an old e-commerce checkout, a Google Workspace tenant, or a mailing list. DNS records may have been added over many years by different providers. The website may run on legacy PHP, old Apache behaviors, hard-coded paths, or an abandoned CMS. Email may depend on forwarding rules no one documented. The business owner may not know which account controls the registrar, which account controls DNS, and which account controls hosting. In this environment, paying a familiar host is a rational insurance premium.
BareMetal’s account portal emphasizes the billing relationship. It exposes account login, billing identifier concepts, and sample invoices associated with BareMetal.com Inc. The company’s contact page lists support email, phone numbers, and business hours, while noting the mailing address is not a business office. This is the support model of a small infrastructure operator: identifiable, reachable, but not built around in-person retail or enterprise field sales.
Domain registration adds a second lock-in mechanism: procedural timing. Expired domains, auto-renew grace periods, redemption periods, transfer locks, and registry rules all create moments where registrar competence matters. In Canadian domain forums, a BareMetal service representative account discussed.CA expiration behavior and the auto-renew period. This is unofficial forum material, not a formal policy source, but commercially it shows why a registrar’s niche knowledge can retain customers. A registrar that understands edge cases around expiration, TBR, and registry states can be valuable even without broad mainstream brand recognition.
The lock-in is also emotional in the narrow business sense. BareMetal’s “About” page explicitly says the company’s first customers were friends and its ethic is to treat customers that way. In a mass hosting environment, this might seem quaint. In the long tail, it is a retention strategy. Small customers do not run formal RFPs for a $15 domain or a modest hosting plan. They renew with the provider who answers the phone, remembers the account, and does not break the old site.
Ownership ambiguity and what the.com sale means
The official evidence supports a narrow conclusion on ownership: BareMetal.ca presents the ongoing operator as Canadian-owned, Canadian-staffed, and physically Canadian, while stating that the BareMetal.com domain was sold. It does not say the company was sold. It does not disclose the buyer, price, debt amount, asset purchase agreement, transition obligations, or whether any customers were transferred. The secondary BBB profile identifies Tom Brown as owner, but this should not be treated as a current substitute for the company registry.
The current commercial use of BareMetal.com points to i3D.net. The BareMetal.com URL redirects to i3D.net’s Bare Metal Cloud page. i3D describes a global bare-metal cloud offering with committed and on-demand capacity, direct server access, automation, private VLANs, anti-DDoS, global points of presence, and custom BGP session support. i3D’s corporate page states that Ubisoft acquired i3D.net in 2018, that i3D continued to operate independently, continued serving external customers, and that the acquisition generated cost savings for Ubisoft workloads that would otherwise have been hosted by public cloud providers.
This is a clear example of domain asset revaluation. For BareMetal.com Inc, the.com was the legacy identity of a Canadian host. For i3D, “baremetal.com” is a category domain aligned with a global product. The same string may have low operational utility for a small incumbent after a.ca transition, but high customer acquisition utility for a global infrastructure seller trying to capture search demand and direct-navigation traffic for bare-metal servers. The buyer does not need the old company’s servers to value the asset. It needs the generic term, the direct-type-in traffic, the search credibility, and the semantic match.
The sale also reveals financial pressure. BareMetal.ca says the.com sale will “repay some debts.” This disclosure is rare among small hosting companies and commercially significant. It suggests the domain was monetized not only because it was surplus, but because it could improve the balance sheet. In the small-host economy, debt can come from hardware refresh cycles, accumulated tax or vendor obligations, operating losses, owner financing, or intangible asset acquisition. Public evidence does not identify the source of the debt, so the careful conclusion is limited: the domain sale was financially important to the ongoing company.
For the successor context, i3D’s network scale changes the economics. i3D’s public pages describe bare-metal capacity as part of a global low-latency network with automation, private networking, and anti-DDoS. PeeringDB and i3D’s peering page present AS49544 as an actively peering network with a formal public policy, NOC requirements, and multi-geography peering expectations. This is not the same business as small shared hosting. It is infrastructure for latency-sensitive workloads such as gaming, interactive services, and distributed applications.
Market structure: from web hosts to infrastructure platforms
BareMetal.com Inc belongs to a generation of hosting companies that emerged when domain names, DNS, email, FTP, UNIX support, and web hosting were bundled together. In that market, the provider’s advantage came from competence and continuity. The customer was not buying primitives; the customer was buying “my website works,” “my domain renews,” and “someone answers when something breaks.”
The modern infrastructure market has separated and recombined these layers. Registrars became a large-scale business and a niche for domain investors. DNS became both a commodity and a premium security service. Email moved to Google, Microsoft, and specialized providers. Web hosting split into shared hosting, managed WordPress, VPS, cloud infrastructure, serverless, and managed platforms. Dedicated servers became “bare metal,” then “bare metal cloud,” then part of hybrid cloud, AI infrastructure, private cloud, and gaming infrastructure narratives.
This transition creates pressure on small hosts. They lose high-growth customer cohorts to cloud platforms and SaaS builders. They face security and compliance burdens that did not exist in the 1990s. Hardware refreshes become less forgiving. IPv4 addresses become more expensive. Customers expect HTTPS, modern control panels, spam filtering, two-factor authentication, automated backups, and instant provisioning. Meanwhile, the host cannot easily raise prices on old customers without increasing churn or support tickets.
But small hosts retain advantages where trust, jurisdiction, and continuity matter. A Canadian customer may prefer a Canadian registrar and host. A domain investor may value a registrar that understands TBR.CA. A heritage site owner may prefer non-disruptive service over modern features. A small organization may prefer phone support to a global cloud’s ticket queue. This is not a high-growth market, but it can be a cash-flow market if managed conservatively.
BareMetal’s official pages show exactly this posture. The company emphasizes affordability, customer service, and a long history. It does not present itself as the lowest-possible-cost mass host or the most advanced global cloud. The operational thesis appears to be continuity. In infrastructure, continuity can be a strategy when the installed base is sticky enough and the cost base disciplined.
Survival in infrastructure
The word “survival” is not decorative here. Hosting companies die in several ways. They can be acquired and absorbed. They can lose routing or data center access. They can fail to update systems and suffer a security collapse. They can lose registrar accreditation or upstream reseller relationships. They can lose key staff. They can become unprofitable when too many customers leave but too much infrastructure remains in place. They can sell the domain and disappear.
BareMetal did not disappear. The.com brand asset was sold, but BareMetal.ca continues to present the operating company, account systems, hosting services, domain services, and Canadian identity. This is a different outcome: asset monetization plus operational continuation.
Survival in infrastructure depends on reducing the number of things that can kill the company at once. A host that owns a data center carries the real estate, power, and facility risk. A host that outsources colocation carries the vendor risk. A host that owns portable address space has routing autonomy but must manage routing complexity. A host that uses reassigned space has less routing burden but more provider dependency. A registrar has recurring revenue but must comply with registry obligations. A domain reseller has less compliance burden but less control. Every choice trades autonomy for cost structure.
The choices observed at BareMetal lean toward survival through specialization and dependency management. It appears to rely on Priority Colo for core network/data center inputs, while retaining customer, registrar, and hosting relationships. It sells domain and web hosting services rather than trying to build a global cloud. It shifted from.com to.ca rather than abandoning the brand entirely. It monetized the generic category domain when the market value of that name likely exceeded its operational value to the legacy host.
This is an economically coherent path for an old infrastructure company. It is not the same as growth. It is adaptation under constraint.
What would change the business picture
The public evidence is thin enough that several unresolved facts would materially alter the assessment or interpretation.
The first is the number of active customers. A registrar/host with a few hundred active accounts is a lifestyle business or winding down. With tens of thousands of domains under management, it is a more valuable renewal base. The public pages show service offerings and continuity, but not active domains under management, hosting accounts, revenue, or churn.
The second is revenue composition. Domain registrations generate predictable but low-margin renewals. Shared hosting can have higher margin if support is low and servers are depreciated. Dedicated or colocated servers can produce higher monthly revenue but require more operational labor and capital discipline. The public evidence supports a domain and web hosting business, but not the current split between shared hosting, VPS, dedicated servers, colocation resale, or pure registrar revenue.
The third is the relationship with Priority Colo. If BareMetal owns hardware in Priority Colo’s space, the economics differ from reselling a managed service. If BareMetal leases servers, margins and migration flexibility differ further. If the reassignment of 67.223.102.0/24 is contractually stable, the host has more continuity. If it is easily revocable or non-transferable, migration risk is higher.
The fourth is the structure of the.com sale. A simple domain name sale is one thing. A sale that includes traffic redirection, customer referrals, transition assistance, brand clauses, or non-compete is another. BareMetal.ca’s statement confirms the.com was sold and debt repayment was a use of proceeds, but not the deal structure.
The fifth is platform security and modernization. The value of a legacy hosting company can be rapidly impaired by outdated control panels, old operating systems, unpatched web stacks, weak account security, or mail reputation problems. Third-party traces of hosted sites and old server headers may suggest legacy infrastructure, but they are not sufficient to judge current internal patching or security level. The key question is whether the company can maintain legacy customer stability without allowing old software to become a systemic risk.
The economics revealed by BareMetal
BareMetal.com Inc reveals five mechanisms easy to miss in the analysis of large cloud companies.
First, infrastructure brands can outlive their original product meaning. BareMetal chose its name to signal low-level technical competence. The market later turned “bare metal” into a standardized product category. The company’s domain then became more valuable to a global bare-metal seller than to the original small host. This is brand option value created by semantic drift.
Second, IPv4 scarcity creates hidden balance-sheet effects. BareMetal’s visible /24 reassignment is not a massive asset on a hyperscale scale, but it is operationally significant. It enables hosting, mail, DNS continuity, and customer isolation. Whether owned, reassigned, or bundled with colocation, addressing capacity affects product design and bargaining power.
Third, customer lock-in in hosting is primarily procedural. It comes from DNS, email, registrar status, old scripts, billing relationships, and fear of downtime, not formal exclusivity. This type of lock-in is weaker than monopoly power, but stronger than a simple price-comparison benchmark.
Fourth, data center dependency is a rational substitute for vertical integration. A small host can buy network and facility quality from a provider like Priority Colo rather than building it. The cost is dependency on the provider’s routing, facility, and business continuity.
Fifth, survival in infrastructure can be economically valuable without being newsworthy. A company that keeps renewing customers, answering support, maintaining domains, and paying its vendors may produce little public evidence. That silence is not the absence of economics. It is the shape a mature long-tail infrastructure business takes.
BareMetal.com Inc matters, therefore, less as a standalone investment target than as a diagnostic case. It shows how the first-generation web hosting stack decomposed into assets: customer relationships, registrar channels, IP allocations, vendor contracts, domain names, and operational know-how. Some of these assets remain with the ongoing Canadian operator. One of them, the BareMetal.com name, appears to have moved into a global bare-metal cloud context. The economics of dedicated infrastructure are visible in this split.
Evidence register
Official BareMetal company pages: BareMetal.ca identifies the company as Canadian web hosting and domain registration specialists since 1995, states that the transition from BareMetal.com to BareMetal.ca was virtually complete as of May 2026, says the.com was sold and the sale proceeds would help repay debts. BareMetal’s “About” page describes the company’s origin in Internet connectivity and UNIX support, its shift to web hosting in 1995, and its incorporation as BareMetal.com Inc in 2000.
BareMetal services and terms: The company’s web services page lists virtual servers, domain registration, secure web services, redundant servers, FTP, mailing lists, SQL databases, and logs. The domain page states that BareMetal has been a CIRA-certified.ca registrar since 2000 and an OpenSRS reseller for other domains since 1999 or 2000. The terms and conditions and registration agreement place backup responsibility on customers, reserve termination rights for security and stability reasons, and limit certain liabilities.
Contact and account evidence: BareMetal’s contact page lists support email, phone numbers, weekday support hours (Pacific Time), and a Victoria mailing address that is not a business office. The account portal shows ongoing account login and billing identifier infrastructure associated with BareMetal.com Inc.
Secondary company evidence: The BBB profile lists BareMetal.com Inc as a corporation, gives a start/incorporation date of June 29, 2000, and names Tom Brown as owner, while the BBB’s own disclaimers mean this should be treated as secondary evidence, not definitive company registry proof. BBB review and complaint pages showed no visible reviews or complaints in this channel.
RIR, WHOIS, BGP, and address evidence: Public WHOIS/RDAP records derived from ARIN identify BareMetal.com Inc, org ID BAREM-2, as the reassigned organization for 67.223.102.0/24 inside Priority Colo’s parent block 67.223.96.0/20. Third-party IP intelligence records link BareMetal hostnames to this range and show routing via AS30176/Priority Colo with valid RPKI at the aggregate level. BGP.tools identifies Priority Colo’s AS30176, upstreams, and originated routes.
ASN 138282 correction: Public records derived from APNIC and BGP directories identify AS138282 as DMRC-AS, Delhi Metro Rail Corporation Limited, India. This does not support attributing AS138282 to BareMetal.com Inc.
Priority Colo and data center evidence: Priority Colo’s official pages describe colocation, dedicated servers, related services, Greater Toronto Area facilities, and network infrastructure. Its network page lists transit, transport, and peering elements, including TorIX and major carriers. PeeringDB identifies AS30176 as Priority Colo with public network attributes. Cologix TOR1 facility page on PeeringDB places Priority Colo in the 151 Front Street ecosystem.
Successor and category domain evidence: BareMetal.com redirects to i3D.net’s Bare Metal Cloud page, which describes dedicated physical servers consumed with cloud-like automation, committed and on-demand models, a public IPv4 address included per server, redundant uplinks, and global network features. i3D states that Ubisoft acquired i3D.net in 2018 while i3D continued to operate independently and serve external customers. i3D’s peering materials and PeeringDB profile describe a global network context much larger than BareMetal’s visible footprint.
Unofficial market traces: Domain and hosting forums, hosting review pages, and user comments mention BareMetal as a Canadian hosting provider or registrar. These are low-weight, unreliable sources for revenue, customer satisfaction, or current operational scale. Their business value is limited to showing community visibility and category perception.
Watchpoints
The first watchpoint is whether BareMetal.ca remains the active operational identity after the.com sale. Continued account portal availability, nameserver continuity, support responsiveness, and domain renewal operations would indicate a stable post-sale transition. Any prolonged outage, nameserver change, or registrar status change would be commercially significant.
The second watchpoint is the fate of 67.223.102.0/24. If BareMetal’s reassigned range is withdrawn, renumbered, transferred, or absorbed into another hosting stack, that would indicate either provider migration, contraction, or restructuring. If it remains stable behind Priority Colo, the continuity thesis strengthens.
The third watchpoint is CIRA registrar status and TBR.CA activity. BareMetal’s registrar role is a key differentiator from a generic legacy web host. Loss of registrar status, reduced TBR visibility, or a shift to pure reseller status would reduce the strategic value of the customer base.
The fourth watchpoint is customer migration after the BareMetal.com sale. The old.com domain had identity value, search value, and trust value. A smooth shift to BareMetal.ca would show that customer relationships are stronger than the domain. Customer confusion, lost renewals, or support escalation would show that the.com was operationally more important than the company’s transition language suggests.
The fifth watchpoint is i3D’s use of BareMetal.com. If i3D continues to use the domain as a category landing page, the transaction should be interpreted as customer acquisition and search-intent capture. If i3D later develops BareMetal.com into a distinct brand, marketplace, or self-service dedicated-server portal, the acquired domain’s value would be higher than a simple redirect suggests.
The sixth watchpoint is ownership disclosure. BareMetal.ca’s public statement establishes Canadian ownership and the.com sale, but not the current corporate shareholders, the domain buyer, price, or any terms. Corporate registry filings, litigation, secured creditor filings, or domain transaction disclosures would materially improve the business picture.
The seventh watchpoint is modernization risk. Legacy hosting businesses can survive for decades, but the cost of security, mail deliverability, SSL automation, two-factor authentication, backup expectations, and software patching increases over time. A visible platform refresh would support long-term survival. Stagnation would increase the likelihood that the remaining value is mostly domains, renewals, and goodwill rather than sustainable hosting infrastructure.