Hosting Journalist

Hosting Journalist Hosting Journalist is a news portal covering the global web & cloud hosting industry. For your daily

Hostingjournalist.com is a news portal covering the global hosting industry with solutions among which cloud servers, dedicated servers virtual servers, reseller hosting, managed hosting, CDN, and colocation.

QScale Starts C$700M AI Data Center Expansion in Quebec City: QScale has started construction on a second building a...
07/06/2026

QScale Starts C$700M AI Data Center Expansion in Quebec City: QScale has started construction on a second building at its Q01 campus in Lévis, Quebec, a C$700 million expansion designed to add 60 MW of IT capacity for AI and high-performance computing workloads, as infrastructure buyers look for dense, liquid-cooled space tied to renewable power and domestic data governance under Canadian law for sensitive enterprise systems.

The build is not just another data hall going vertical. Q01 Building B is being framed as a facility capable of handling accelerated computing systems in the NVIDIA GB300 class, with support for liquid-cooled racks at 600 kW or more per cabinet. That is a very different engineering problem from the 10 kW, 20 kW, even 80 kW rack densities that shaped much of the previous cloud era.

And it narrows the buyer pool. These are not casual colocation customers. This is infrastructure for hyperscale AI, research workloads, sovereign compute initiatives, financial modeling, large enterprise AI training, and the growing number of organizations that have discovered their AI strategy now has a substation problem.

QScale is a portfolio company of Infrastructure at Goldman Sachs Alternatives, which gives the project a certain capital-market context. AI data centers are increasingly behaving like infrastructure assets, but with software-cycle risk attached. Chips change quickly. Cooling assumptions change. Power procurement becomes strategic. Customers want optionality while developers need long-duration commitments.

Hard to square neatly.

Power Comes First

Quebec gives QScale an obvious advantage: a hydro-dominated grid and cold climate. For data center operators, that means a cleaner power story and potentially better efficiency. For customers under pressure to explain the emissions impact of AI workloads, it helps. It does not remove the hard questions.

A 60 MW IT load is substantial. Local grid capacity, interconnection timing, backup power, water usage, and heat management still have to work in practice. The company says the campus uses waste-heat recovery, with thermal energy redirected toward projects such as greenhouse agriculture. Useful, if executed at scale. But heat reuse often sounds simpler in announcements than in municipal planning documents. It needs nearby demand, reliable thermal distribution, and economics that survive outside a diagram.

Still, the direction is important. AI infrastructure is forcing data center operators to treat heat as a resource, not only a byproduct. Regulators will notice. So will communities.

Sovereign Compute Angle

The Canadian-soil argument is also doing more work here than it might have five years ago. Enterprises, universities, health systems, government bodies, and regulated industries increasingly care where AI models run and where sensitive data sits. QScale is presenting Q01 as a domestic alternative to foreign-hosted infrastructure, under Canadian law and powered by local renewable energy.

That will resonate with public-sector buyers and regulated enterprises. It may also appeal to AI companies trying to sell into those accounts.

But sovereignty is not solved by geography alone. Hardware supply chains remain global. AI software stacks are often American. Cloud dependencies can remain embedded even when servers sit in Quebec. Buyers will still need to examine operational control, access rights, support arrangements, encryption, auditability, and vendor dependencies.

Canada wants more sovereign AI capacity. Quebec wants digital infrastructure jobs. QScale says around 300 workers will be on site at peak construction, with permanent roles following once the building enters service. That is politically useful. It also makes the project part of a broader competition among regions trying to turn power availability into digital industrial policy.

Density Risk

The most technically aggressive claim is the readiness for 600 kW-plus racks. That suggests a facility designed around liquid cooling from the start, not retrofitted after customers arrive with hotter equipment than expected. For AI infrastructure buyers, that matters because retrofit risk is expensive and ugly. Downtime. Layout compromises. Cooling loops added late. Power distribution that no longer matches the hardware roadmap.

QScale says the building can support both ultra-dense liquid-cooled deployments and conventional air-cooled servers in the same facility. Flexibility is attractive, but mixed environments can complicate operations. Different maintenance regimes. Different failure modes. Different customer expectations around redundancy and service windows.

For developers, the larger market signal is blunt. The next generation of data centers is less about square footage and more about engineered capacity. Can the site take the power? Can it remove the heat? Can it support the next accelerator cycle without ripping up the floor?

QScale is now trying to answer those questions in Lévis, with C$700 million of construction risk attached.

Executive Insights FAQ

What changes for enterprise infrastructure buyers?

QScale adds another Canadian option for high-density AI hosting, but buyers should examine cooling architecture, interconnection timelines, service-level terms, and operational control.

Why is Quebec strategically relevant?

Quebec offers renewable-heavy power and colder ambient conditions, which can improve energy positioning for AI workloads with intense electricity and cooling requirements.

How credible is the sovereignty argument?

Domestic hosting helps with legal jurisdiction and procurement requirements, but enterprises still need clarity on vendor access, software dependencies, encryption, and audit rights.

What is the main ex*****on risk?

The project depends on delivering very high-density liquid-cooled environments reliably, while aligning grid capacity, construction schedules, hardware availability, and customer commitments.

Why should investors care?

AI facilities can command strong demand, but returns depend on utilization, power pricing, tenant quality, financing costs, and avoiding stranded designs.

http://dlvr.it/TSw4Hr

Gartner Warns CISOs of Four Cyber Threats Redrawing Enterprise Risk: Gartner is warning security chiefs that four th...
07/06/2026

Gartner Warns CISOs of Four Cyber Threats Redrawing Enterprise Risk: Gartner is warning security chiefs that four threat categories - deepfakes, compromised AI applications, prompt injection and software supply chain attacks - now deserve urgent attention because attackers are moving faster than most corporate defenses can adapt, especially as generative AI systems rapidly spread from pilot projects into production workflows, employee tools and customer-facing services at scale.

The message is blunt enough, though not especially surprising. Enterprises spent the last 18 months wiring generative AI into software development, customer support, internal search, recruitment, analytics, sales enablement and executive workflows. Many did it before security teams had a full inventory of what was being built. Some did it through sanctioned platforms. Some through browser tabs, API keys, plug-ins, workflow automation tools and enthusiastic employees with procurement cards.

Now Gartner is effectively telling CISOs to stop treating AI as a separate innovation track and start treating it as production infrastructure with production-grade failure modes.

The list matters because it is not just about model safety. It is about access control, identity, vendor risk, software integrity, employee verification, runtime monitoring and the boring mechanics of security operations. AI has not replaced old cyber problems. It has made them wider, faster and harder to see.

John Watts, a vice president analyst at Gartner, said frontier AI companies’ security initiatives are adding more noise to an already crowded threat environment. Security leaders, he said, need to find the real threat signal. Fair enough. The harder question is whether the average enterprise security team has enough authority, telemetry and budget to do anything meaningful once it finds it.

AI Systems Become Targets

AI application compromise may be the least theatrical threat on Gartner’s list, but probably the most immediately operational. Enterprises are putting AI tools in front of employees, customers and partners. They are also connecting them to data stores, ticketing systems, code repositories, HR platforms, CRM records and internal knowledge bases.

Useful, yes. Also awkward.

An internal chatbot with weak access controls can become a data exposure mechanism. A custom agent with overbroad permissions can execute actions it should only recommend. A third-party AI integration can inherit sensitive credentials. None of this requires cinematic hacking. Sometimes it requires ordinary misconfiguration, rushed deployment and unclear ownership between security, engineering, data science and business units.

Gartner wants CISOs to apply secure development practices and threat modeling to AI applications. That sounds basic. It is also not how many AI deployments have been handled. A lot of them grew out of experiments. Then they became “strategic.” Then they landed in production with unclear documentation.

The commercial effect is already visible. AI security vendors are crowding into the gap, selling runtime monitoring, model firewalling, data loss prevention for prompts, agent security and governance tooling. Buyers should expect overlap, immature product categories and inflated claims. Still, the underlying need is real. Enterprises need to know which AI systems exist, what they can access, who owns them, what data they process and how their behavior changes under attack.

Gartner points to its TRiSM framework - trust, risk and security management - as one route for embedding AI-specific controls into development. In practice, many organizations will start with less elegant work: asset discovery, data classification, purpose-based access control and monitoring for abnormal AI behavior. Not glamorous. Necessary.

Identity Gets Weirder

Deepfakes are no longer a novelty risk filed under executive fraud. Gartner says generative AI has made fake voice, video and image content cheaper, more realistic and easier to produce, including in real time. That changes the attack surface around meetings, hiring, biometric verification and payment approvals.

The problem is that detection alone is a weak answer. Synthetic media detection works unevenly, adversaries adapt, and many business processes still rely on human trust cues that were never designed for adversarial video calls.

Recruitment is one exposed area. Remote hiring already depends on digital identity checks, interviews and document workflows. Add convincing real-time impersonation and the hiring process becomes a security boundary, not just an HR function. Finance approvals face similar pressure. So do help desks, executive assistants and managed service providers handling privileged requests.

Gartner’s guidance here is more procedural than magical: strengthen business processes, improve employee awareness, protect biometric verification against presentation and injection attacks, and secure online meetings with conditional access and stronger authentication. That means fewer informal exceptions. More friction. More logging. Possibly more annoyed executives.

There is a regulatory angle too. If biometric systems can be fooled, organizations may face uncomfortable questions about consent, identity assurance and liability. Regulators are already nervous about AI-generated deception. Enterprises using face or voice verification will need to show they understand not just accuracy, but attack resistance.

Supply Chains Still Break

Software supply chain security has been a board-level concern for years, but AI expands the inventory problem. Gartner argues that generative AI offerings will accelerate attacks through open source weaknesses and modern development pipelines.

The old problem was third-party code. The newer one includes container images, AI models, training data, plug-ins, build artifacts, agent workflows and automated coding outputs. Developers can move faster. Attackers can, too. Security teams are left trying to determine whether the thing entering production is trusted, current, signed, scanned and actually the thing they think it is.

Gartner calls for software bills of materials and AI bills of materials from vendors, risk assessment of components before deployment, curated repositories, branch protection, artifact signing, least-privilege access to build systems and runtime monitoring of agentic tools.

None of that is controversial. None of it is simple at scale.

Large enterprises already struggle to maintain accurate software inventories. Smaller suppliers may not be able to provide meaningful SBOMs, let alone AIBOMs. Procurement teams may ask for them. Vendors may send PDFs. Security teams may receive documents they cannot operationalize. Investors should note the familiar pattern: compliance demand creates a tooling market, but operational value depends on integration into engineering workflows.

Prompt Injection Persists

Prompt injection is the most AI-specific item on Gartner’s list, and maybe the one most likely to frustrate executives looking for a clean control. The attack involves manipulating model inputs so an AI system ignores intended instructions, reveals sensitive information, triggers unauthorized actions or bypasses guardrails.

The risk rises as large language models gain access to tools. A chatbot that only drafts text is one thing. An agent that can query databases, open tickets, modify records or interact with external services is another. Prompt injection then becomes less about embarrassing outputs and more about unauthorized workflow ex*****on.

Gartner recommends input validation, sanitization, prompt injection testing during development, monitoring for abnormal model behavior and runtime guardrails. Good. But no one should pretend this is equivalent to patching a known CVE. LLMs interpret language probabilistically. Attackers can hide instructions in documents, web pages, emails, tickets and user content. Controls will reduce risk. They will not eliminate it.

For developers, this means AI systems need design patterns closer to zero trust. Limit what the model can access. Separate instructions from untrusted content. Require confirmation for sensitive actions. Log decisions. Test adversarially. Expect failure.

For infrastructure buyers and operators, the spending case is becoming clearer but more complicated. AI security is not one purchase. It touches IAM, data governance, application security, CI/CD, endpoint controls, collaboration platforms and vendor management. The budget fight will be ugly in organizations where AI programs report into innovation or business units while the risk lands on the CISO’s desk.

Gartner’s warning is less a prediction than a status report. The enterprise attack surface has been redrawn while many governance models are still catching up. Some companies will respond with frameworks and committees. Some will buy tools. Some will quietly discover that nobody knows how many AI applications are already running inside the business.

Executive Insights FAQ

Why should enterprise leaders prioritize these risks now?

AI tools are moving into operational systems faster than security governance can mature, increasing exposure across identity, data access, development workflows and vendor dependencies.

Where will enterprises feel the cost first?

Costs will likely appear in security tooling, process redesign, employee verification, software inventory work, developer training and slower approval paths for sensitive AI-enabled systems.

Are AI security startups enough to solve this?

Specialist vendors can help with monitoring and controls, but buyers still need asset ownership, data classification, access discipline and integration with existing security operations.

What is the biggest adoption barrier?

The hardest issue is organizational accountability. AI systems often span engineering, data, legal, procurement and business teams without one owner responsible for security outcomes.

How should boards interpret Gartner’s warning?

Boards should treat AI security as enterprise risk management, not experimentation oversight, and demand evidence of inventories, controls, testing and incident response readiness.

http://dlvr.it/TSw52X

DayOne Raises $4.5B For AI Data Center Expansion Plan: DayOne Data Centers has closed a $4.5 billion Series C, givin...
07/06/2026

DayOne Raises $4.5B For AI Data Center Expansion Plan: DayOne Data Centers has closed a $4.5 billion Series C, giving the Singapore-based data center developer fresh equity for an expansion across Asia and Europe as hyperscalers hunt for AI capacity. Existing backers Coatue and Hillhouse led the round, joined by Indonesia Investment Authority and Achi Capital Partners, with more financing likely ahead as demand rises again.

The number is large enough to say something about where the data center market now sits. Not in a normal real estate cycle. Not even in a conventional cloud infrastructure cycle. AI has turned capacity into a financial product, an energy negotiation, a land question, and a sovereignty problem all at once.

DayOne says it has secured more than 1.5 GW of contracted capacity across Asia Pacific and Europe since launching in 2022. That is not a small pipeline. It also means the company is now operating in the uncomfortable zone where signing capacity is easier than delivering it. Power, grid access, cooling, permitting, fiber routes, and customer concentration all start to matter more than glossy renderings of AI-ready campuses.

Expansion With Constraints

The planned markets - Singapore, Malaysia, Indonesia, Thailand, Japan, Hong Kong, Finland, and Spain - tell the story. Enterprises and hyperscalers want regional capacity close to users, regulators, and data-residency requirements. Singapore remains strategically useful but physically constrained. Malaysia and Indonesia offer land and power options, though ex*****on risk rises quickly. Japan and Hong Kong bring connectivity and enterprise demand, but also cost and complexity. Finland and Spain suggest a European angle around energy availability, latency routes, and diversification.

The investor mix is also notable. Coatue and Hillhouse remaining the two largest owners gives DayOne growth-capital credibility. Indonesia Investment Authority’s participation adds a sovereign dimension. Infrastructure is increasingly national policy by another name. Data centers used to be technical facilities with landlords attached. Now governments care about who builds them, where workloads sit, and how much electricity they absorb.

Debt Is Waiting

DayOne also left the door open to additional debt and equity financing in public and private markets, depending on market conditions. Translation: $4.5 billion is a start, not the full bill.

AI campuses consume capital brutally. Land acquisition is only the first line item. Substations, long-lead electrical gear, cooling systems, backup generation, networking, and customer-specific fit-outs can stretch timelines and budgets. If interest rates remain awkward, the economics get thinner. If power contracts become harder to secure, growth becomes less about fundraising and more about utility politics.

For hyperscalers and large enterprises, the news adds another supplier to a market where capacity is scarce but not interchangeable. “AI-ready” still needs scrutiny. Buyers will ask about actual rack densities, liquid-cooling support, grid redundancy, sustainability reporting, and delivery schedules. Investors will ask whether contracted capacity becomes revenue on time.

Fast growth in data centers has a way of exposing every hidden dependency. Especially power. Especially now.

Executive Insights FAQ

What changes for enterprise infrastructure buyers?

DayOne’s funding may increase regional capacity options, but buyers still need to validate power availability, cooling design, deployment timelines, and contractual flexibility.

Why does this matter for hyperscalers?

Hyperscalers need large, geographically distributed AI capacity. DayOne’s footprint could reduce concentration risk, though ex*****on across multiple jurisdictions remains difficult.

What is the main operational risk?

Electricity access is the binding constraint. Capital can be raised faster than grids, substations, and permitting processes can be upgraded.

How should investors read the financing?

The round signals strong demand for AI infrastructure exposure, but future returns depend on delivery discipline, customer concentration, leverage, and energy costs.

What regulatory issues could emerge?

Data sovereignty, environmental approvals, grid strain, and foreign ownership scrutiny may become more important as campuses expand across sensitive regional markets.

http://dlvr.it/TSw3l9

Arpio Raises $15M to Expand Automated Cloud Recovery Tooling: Arpio has raised $15 million in Series A funding to expa...
07/06/2026

Arpio Raises $15M to Expand Automated Cloud Recovery Tooling: Arpio has raised $15 million in Series A funding to expand its automated cloud recovery platform, as enterprises face mounting pressure to prove they can restore critical workloads after ransomware, outages, mistakes, or infrastructure failures. The round was co-led by S3 Ventures and Paladin Capital Group, with Draper Associates and others participating in the financing being announced.

The company is selling into a market that has become less patient with traditional disaster recovery. Backups are not enough. Recovery time objectives written into governance documents are not enough either, particularly when boards, insurers, regulators, and large customers increasingly want evidence that systems can come back without days of improvisation.

Arpio’s claim is that cloud recovery needs to be native, automated, and continuously tested. Not a binder. Not a consulting exercise. Not a once-a-year simulation everyone dreads.

The company, founded in 2020 by Doug Neumann and Shaw Terwilliger, focuses on restoring cloud-hosted applications after ransomware, destructive attacks, accidental changes, provider outages, and infrastructure failures. The fresh capital is earmarked for expansion across AWS and Microsoft Azure, broader support for Google Cloud, and additional work around AI-native services.

That last phrase will attract attention. It should also attract scrutiny.

Recovery Gets Repriced

The economics of downtime have changed. More customer-facing systems now run across distributed cloud environments. More internal operations depend on APIs, managed databases, identity services, queues, object storage, and application-specific infrastructure that does not map cleanly onto older disaster recovery tooling.

Then came ransomware. Then cloud sprawl. Then AI workloads, which bring their own dependency chains, data pipelines, model services, orchestration layers, and expensive compute commitments. Failures become harder to understand. Recovery becomes less about restoring a server and more about reassembling a working business process from cloud services that may have drifted, been encrypted, misconfigured, deleted, or regionally unavailable.

Arpio says it can help companies recover critical systems in minutes rather than days and validate recovery plans before incidents occur. The validation part may matter more than the speed claim. Enterprises have heard aggressive recovery promises before. The real question is whether they can test failover end to end without damaging production, creating side effects, or consuming so much staff time that testing gets postponed until after the next audit.

Arpio says its platform automates failover testing without production impact. For infrastructure buyers, that addresses a persistent weakness in resilience programs: plans often exist, but confidence is thin. Teams do not test frequently because testing is risky, manual, political, and expensive.

Cloud-Native, With Caveats

Arpio is positioning itself against older disaster recovery products that were built for a different infrastructure model. That is plausible. Cloud environments are API-driven, dynamic, and full of dependencies that traditional replication tools may not understand well.

Still, cloud-native recovery is not magic. Restoring a workload requires knowing what “working” means. Networking, IAM, secrets, databases, storage states, security policies, DNS records, application dependencies, third-party services, and compliance constraints all have to line up. In mature environments, some of that is codified. In many companies, some of it lives in tribal memory, Terraform that has not been applied cleanly in months, or tickets nobody wants to reopen.

The platform’s value will depend on how well it handles those ugly realities. Multi-account AWS estates. Azure environments shaped by corporate identity policies. Hybrid dependencies. Regional data residency rules. Human approvals. Change windows. Systems that should have been retired but still process revenue.

The funding round gives Arpio more room to pursue those problems, but also raises expectations. It is no longer enough to be a useful recovery tool for cloud teams with clean architectures. The company will need to prove usefulness in enterprise environments where cloud adoption happened in waves, often under different governance regimes.

AI Raises The Stakes

The company and its investors are linking the funding to AI-native infrastructure. That framing fits the current market, but it is not just decoration. AI systems can increase operational fragility. They create new workloads, faster development cycles, heavier data movement, and more automation around infrastructure changes. They can also generate mistakes at scale when internal tools, agents, or scripts make incorrect assumptions.

That makes recoverability a board-level issue, not only an infrastructure concern. If AI services become embedded in customer support, fraud detection, software development, logistics, pricing, or medical workflows, downtime becomes commercially visible quickly.

But “AI-native recovery” will need definition. Does it mean recovering AI application stacks? Protecting vector databases, model endpoints, orchestration frameworks, and GPU-backed environments? Using AI to automate recovery decisions? All of the above? Buyers will press for detail because the operational risk profile differs sharply across those scenarios.

There is also a governance angle. Automated recovery sounds attractive until it moves data into the wrong region, restores a vulnerable configuration, reconnects compromised services, or violates retention obligations. Resilience and compliance can collide. Fast recovery is only useful if it is also controlled recovery.

Proof Before Crisis

Paladin Capital Group’s involvement signals how closely resilience is now tied to cybersecurity purchasing. S3 Ventures’ co-lead role adds growth-market validation. Other participants include Draper Associates, Uncorrelated, Valor Ventures, CreativeCo Capital, and Lookout Ventures.

Investor interest is not surprising. Cyber resilience has become a spending category because prevention keeps failing. Security buyers still buy detection and response, but CFOs and boards increasingly ask a colder question: what happens after compromise?

Arpio’s answer is automated recovery and continuous proof. That puts it near several overlapping categories: disaster recovery, cyber recovery, cloud resilience, business continuity, infrastructure automation, and compliance evidence. Crowded territory. Large incumbents will not ignore it. Cloud providers also have native services that can absorb parts of the story, especially for customers willing to stay inside one ecosystem.

Arpio’s opening may be operational specificity. If it can recover complex cloud applications faster, test plans more frequently, and provide evidence that auditors and customers accept, it has a sharper role than generic backup or observability vendors.

The unresolved issue is trust. During an incident, teams do not want novelty. They want known procedures, tested paths, escalation clarity, and tools that do not require heroic interpretation. Arpio is arguing that automation can reduce chaos. Maybe. But automation introduced during crisis can also amplify errors if assumptions are wrong.

The company now has $15 million more to make its case across AWS, Azure, Google Cloud, and AI-heavy environments. That is enough to expand product and market reach. Not enough to change enterprise behavior by itself.

Recovery buying is conservative. For good reason. Nobody wants to discover the fine print while the business is down.

Executive Insights FAQ

What does Arpio’s funding indicate about cloud resilience spending?

It signals buyer demand for tested recovery capabilities, especially where cyber insurance, customer contracts, and board oversight now require evidence beyond backup availability.

How should enterprises evaluate automated recovery platforms?

They should test full application restoration, dependency mapping, access controls, audit evidence, regional compliance, rollback behavior, and performance under realistic failure scenarios.

Why is AI relevant to cloud recovery?

AI workloads add fast-changing infrastructure, data dependencies, and automation risks. Recovery tools must account for these systems before they become business-critical.

Where could Arpio face adoption barriers?

Enterprises with fragmented cloud estates, inconsistent infrastructure-as-code, unclear ownership, or strict data residency rules may struggle to automate recovery safely.

What should investors watch next?

Customer expansion across multi-cloud environments, repeatable recovery validation outcomes, enterprise retention, and whether cloud providers absorb similar capabilities into native services.

http://dlvr.it/TSw44B

Adres

Coehoornsingel 58
Zutphen
7201AD

Telefoon

+31630491407

Website

Meldingen

Wees de eerste die het weet en laat ons u een e-mail sturen wanneer Hosting Journalist nieuws en promoties plaatst. Uw e-mailadres wordt niet voor andere doeleinden gebruikt en u kunt zich op elk gewenst moment afmelden.

Contact

Stuur een bericht naar Hosting Journalist:

Snelkoppelingen

Delen