×
GM’s Cruise Cars Are Back on the Road in Three US States—But Not for Ride-Hailing

GM’s Cruise Cars Are Back on the Road in Three US States—But Not for Ride-Hailing

Tech-news , , ,

Cruise robotaxis are back on the road… well, kind of. Though General Motors pulled the plug on its self-driving taxi business last year, the automaker has been quietly repurposing a few of the vehicles as it seeks to develop new driver-assistance technologies.

This week, WIRED spotted a GM Bolt electric hatchback on the San Francisco-Oakland Bay Bridge, and later saw a similar vehicle on Interstate 880 near Oakland. In each instance, the car was being driven by a human. But it held equipment on the roof such as lidar sensors that resembled the setup from the Cruise ride-hailing system. The vehicle had “Mint” written on the hood, but didn’t include any visually apparent Cruise branding.

GM spokesperson Chaiti Sen confirms to WIRED that the company is indeed “using a limited number of Cruise Bolt vehicles on select highways in Michigan, Texas and Bay Area for testing with trained drivers to further develop simulation models and advanced driver assistance systems.” She adds, “This is internal testing and does not involve public passengers.”

GM removed the orange-and-white Cruise logo from the cars’ sides after it took full ownership of the unit in February, she says. The recent activity began in Michigan and Texas in February and the San Francisco Bay Area-region in mid-April, Sen says. Cruise had named each vehicle in its fleet, and Sen confirmed that “Mint” has been among the vehicles newly active in the Bay Area.

The testing shows for the first time how GM is beginning to give a second life to a fleet of no less than hundreds of vehicles left over from a costly project that ran aground.

GM initially acquired a majority stake in San Francisco-based Cruise in 2016, and invested more than $8 billion into developing a robotaxi service. The operation was off to a fast start and eyeing a rapid expansion until October 2023, when a Cruise vehicle struck a pedestrian in San Francisco who had just been hit by a human-driven vehicle.

In the aftermath of the incident, Cruise misled state regulators, lost a key permit, halted operations, and laid off a quarter of its workers.

After some attempts to restart the business, GM announced this past December that the experiment would be cancelled altogether. At the time, GM CEO Mary Barra told analysts that running a robotaxi fleet was an expensive distraction from the business of making cars.

But the technology behind Cruise is helping improve the roughly 7-year-old Super Cruise system found in some GM cars. It aims to help drivers stay in and change lanes, or apply the emergency brake without needing to use their hands.

Several automakers are racing to develop cars that offload an increasing amount of driving tasks to computers. GM claims about 60 percent of its 360,000 Super Cruise customers regularly make use of the capability.

In the US, the robotaxi industry has been dominated by Waymo, though Elon Musk’s Tesla and Amazon’s Zoox are among those continuing to try to catch up.

GM’s repurposed Bolts blend into San Francisco-area roads, on which cars with heavy-duty computer gear attached to roof, back, and sides have become commonplace. They include not only companies testing sensors and algorithms, but also map providers collecting data and hobbyists attempting to upgrade their personal rides.

Source link
#GMs #Cruise #Cars #Road #StatesBut #RideHailing

Tag

Related Posts

Anthropic said Thursday that an internal investigation uncovered three incidents in which its AI model Claude breached the systems of three organizations while conducting cybersecurity tests. The investigation, and disclosure, comes more than a week after OpenAI disclosed that one of its unreleased models breached Hugging Face’s systems during internal testing.

In all three cases, a Claude model reached the internet from within a testing environment while interacting with a third party and then gained unauthorized access to the live systems of these organizations, Anthropic said in a blog post, describing what it found and what the company plans to change to prevent this from happening again.

Anthropic said the OpenAI episode earlier this month prompted the company to conduct its own cybersecurity evaluation. It specifically looked for evidence that Claude had accessed the internet from within testing environments, which are designed to act as sandboxes and keep models isolated.

Among the 141,006 evaluation runs it reviewed, the AI lab found three incidents in which its model accessed the internet while interacting with Irregular, one of its third-party partners. Anthropic said the access traced back to a misconfiguration in the evaluation environment run with Irregular. It called this a “misunderstanding” between the two companies over whether the test setup had internet access, when in fact it did.

Anthropic said it isn’t placing blame and is “approaching the fixes as if the responsibility were ours alone,” while observing that Irregular is conducting its own separate investigation.

Because of that open connection, the model gained unauthorized access to the production infrastructure of three different organizations. Anthropic said the incidents involved three different Claude models: Opus 4.7, Mythos 5, and an internal research test model.

Notably, Anthropic said that in each of these cases “Claude was explicitly told by our prompt that it had no internet access.” It appears that the AI model assumed real-world systems to be part of the exercise it was asked to perform.

That assumption didn’t hold up uniformly, as it turns out. The three models didn’t behave the same way once evidence emerged that their targets were real, which Anthropic flagged as one of the more eye-opening findings Thursday.

Opus 4.7, the oldest of the three, recognized that it had reached a real production system in all four runs of that incident. In two of them, it rationalized that the real company must somehow be part of the exercise, but in all four, it kept attacking anyway, including pulling credentials and touching a database of production data. Mythos 5 also picked up on signs that it was on the real internet, but it talked itself back into believing it was still in a simulation, going on to publish a malicious software package to the public Python software registry PyPI, which was then downloaded and run by outside systems before being caught. Only the internal research test model, Anthropic’s newest, stopped on its own once it concluded the target was real.

In response, Anthropic said significant controls must be placed on these kinds of evaluations if powerful AI models are involved, echoing some sentiments within the cybersecurity community.

The company also noted that Claude was running without the additional safety monitoring and classifiers it deploys on generally available models — safeguards it said would have blocked the behavior, because the evaluations are designed to measure the underlying model’s raw capabilities.

Importantly, Anthropic said it found no evidence of any model “pursuing a goal of its own” and instead merely tried to complete the task it was asked to do.

Though comparisons between the mishaps of these fiercely competitive companies are inevitable, Anthropic in its blog post drew a clear distinction between its cybersecurity tests and those of OpenAI, noting where OpenAI’s model exploited an unknown software vulnerability to break out of its test environment, Anthropic’s models instead reached the internet through a path that had, by mistake, been left open.

Anthropic also drew a distinction between itself and OpenAI by noting that it discovered the incidents itself, through a proactive review, and that the two affected organizations it was able to reach hadn’t previously detected the activity or flagged it to Anthropic. (In contrast, Hugging Face detected the recent intrusion of its own systems first; it was only in the following days that OpenAI identified and disclosed that its own AI agent was the perpetrator.)

The company added that it’s now working with the independent evaluation group METR on a third-party review of the incidents.

OpenAI’s accidental breach of Hugging Face, which was the first verifiable case of an AI lab losing control of its model, has sparked a string of wildly differing reactions from the industry and politicians. This latest disclosure from Anthropic ensures the debate over AI models and security will continue.

When you purchase through links in our articles, we may earn a small commission. This doesn’t affect our editorial independence.

#Anthropic #models #breached #companies #security #tests #TechCrunchAnthropic,OpenAI">Anthropic says its own AI models breached three companies during security tests | TechCrunch Anthropic said Thursday that an internal investigation uncovered three incidents in which its AI model Claude breached the systems of three organizations while conducting cybersecurity tests. The investigation, and disclosure, comes more than a week after OpenAI disclosed that one of its unreleased models breached Hugging Face’s systems during internal testing. In all three cases, a Claude model reached the internet from within a testing environment while interacting with a third party and then gained unauthorized access to the live systems of these organizations, Anthropic said in a blog post, describing what it found and what the company plans to change to prevent this from happening again. Anthropic said the OpenAI episode earlier this month prompted the company to conduct its own cybersecurity evaluation. It specifically looked for evidence that Claude had accessed the internet from within testing environments, which are designed to act as sandboxes and keep models isolated. Among the 141,006 evaluation runs it reviewed, the AI lab found three incidents in which its model accessed the internet while interacting with Irregular, one of its third-party partners. Anthropic said the access traced back to a misconfiguration in the evaluation environment run with Irregular. It called this a “misunderstanding” between the two companies over whether the test setup had internet access, when in fact it did. Anthropic said it isn’t placing blame and is “approaching the fixes as if the responsibility were ours alone,” while observing that Irregular is conducting its own separate investigation. Because of that open connection, the model gained unauthorized access to the production infrastructure of three different organizations. Anthropic said the incidents involved three different Claude models: Opus 4.7, Mythos 5, and an internal research test model. Notably, Anthropic said that in each of these cases “Claude was explicitly told by our prompt that it had no internet access.” It appears that the AI model assumed real-world systems to be part of the exercise it was asked to perform. That assumption didn’t hold up uniformly, as it turns out. The three models didn’t behave the same way once evidence emerged that their targets were real, which Anthropic flagged as one of the more eye-opening findings Thursday. Opus 4.7, the oldest of the three, recognized that it had reached a real production system in all four runs of that incident. In two of them, it rationalized that the real company must somehow be part of the exercise, but in all four, it kept attacking anyway, including pulling credentials and touching a database of production data. Mythos 5 also picked up on signs that it was on the real internet, but it talked itself back into believing it was still in a simulation, going on to publish a malicious software package to the public Python software registry PyPI, which was then downloaded and run by outside systems before being caught. Only the internal research test model, Anthropic’s newest, stopped on its own once it concluded the target was real. In response, Anthropic said significant controls must be placed on these kinds of evaluations if powerful AI models are involved, echoing some sentiments within the cybersecurity community. The company also noted that Claude was running without the additional safety monitoring and classifiers it deploys on generally available models — safeguards it said would have blocked the behavior, because the evaluations are designed to measure the underlying model’s raw capabilities. Importantly, Anthropic said it found no evidence of any model “pursuing a goal of its own” and instead merely tried to complete the task it was asked to do. Though comparisons between the mishaps of these fiercely competitive companies are inevitable, Anthropic in its blog post drew a clear distinction between its cybersecurity tests and those of OpenAI, noting where OpenAI’s model exploited an unknown software vulnerability to break out of its test environment, Anthropic’s models instead reached the internet through a path that had, by mistake, been left open. Anthropic also drew a distinction between itself and OpenAI by noting that it discovered the incidents itself, through a proactive review, and that the two affected organizations it was able to reach hadn’t previously detected the activity or flagged it to Anthropic. (In contrast, Hugging Face detected the recent intrusion of its own systems first; it was only in the following days that OpenAI identified and disclosed that its own AI agent was the perpetrator.) The company added that it’s now working with the independent evaluation group METR on a third-party review of the incidents. OpenAI’s accidental breach of Hugging Face, which was the first verifiable case of an AI lab losing control of its model, has sparked a string of wildly differing reactions from the industry and politicians. This latest disclosure from Anthropic ensures the debate over AI models and security will continue. When you purchase through links in our articles, we may earn a small commission. This doesn’t affect our editorial independence.#Anthropic #models #breached #companies #security #tests #TechCrunchAnthropic,OpenAI

Hugging Face’s systems during internal testing.

In all three cases, a Claude model reached the internet from within a testing environment while interacting with a third party and then gained unauthorized access to the live systems of these organizations, Anthropic said in a blog post, describing what it found and what the company plans to change to prevent this from happening again.

Anthropic said the OpenAI episode earlier this month prompted the company to conduct its own cybersecurity evaluation. It specifically looked for evidence that Claude had accessed the internet from within testing environments, which are designed to act as sandboxes and keep models isolated.

Among the 141,006 evaluation runs it reviewed, the AI lab found three incidents in which its model accessed the internet while interacting with Irregular, one of its third-party partners. Anthropic said the access traced back to a misconfiguration in the evaluation environment run with Irregular. It called this a “misunderstanding” between the two companies over whether the test setup had internet access, when in fact it did.

Anthropic said it isn’t placing blame and is “approaching the fixes as if the responsibility were ours alone,” while observing that Irregular is conducting its own separate investigation.

Because of that open connection, the model gained unauthorized access to the production infrastructure of three different organizations. Anthropic said the incidents involved three different Claude models: Opus 4.7, Mythos 5, and an internal research test model.

Notably, Anthropic said that in each of these cases “Claude was explicitly told by our prompt that it had no internet access.” It appears that the AI model assumed real-world systems to be part of the exercise it was asked to perform.

That assumption didn’t hold up uniformly, as it turns out. The three models didn’t behave the same way once evidence emerged that their targets were real, which Anthropic flagged as one of the more eye-opening findings Thursday.

Opus 4.7, the oldest of the three, recognized that it had reached a real production system in all four runs of that incident. In two of them, it rationalized that the real company must somehow be part of the exercise, but in all four, it kept attacking anyway, including pulling credentials and touching a database of production data. Mythos 5 also picked up on signs that it was on the real internet, but it talked itself back into believing it was still in a simulation, going on to publish a malicious software package to the public Python software registry PyPI, which was then downloaded and run by outside systems before being caught. Only the internal research test model, Anthropic’s newest, stopped on its own once it concluded the target was real.

In response, Anthropic said significant controls must be placed on these kinds of evaluations if powerful AI models are involved, echoing some sentiments within the cybersecurity community.

The company also noted that Claude was running without the additional safety monitoring and classifiers it deploys on generally available models — safeguards it said would have blocked the behavior, because the evaluations are designed to measure the underlying model’s raw capabilities.

Importantly, Anthropic said it found no evidence of any model “pursuing a goal of its own” and instead merely tried to complete the task it was asked to do.

Though comparisons between the mishaps of these fiercely competitive companies are inevitable, Anthropic in its blog post drew a clear distinction between its cybersecurity tests and those of OpenAI, noting where OpenAI’s model exploited an unknown software vulnerability to break out of its test environment, Anthropic’s models instead reached the internet through a path that had, by mistake, been left open.

Anthropic also drew a distinction between itself and OpenAI by noting that it discovered the incidents itself, through a proactive review, and that the two affected organizations it was able to reach hadn’t previously detected the activity or flagged it to Anthropic. (In contrast, Hugging Face detected the recent intrusion of its own systems first; it was only in the following days that OpenAI identified and disclosed that its own AI agent was the perpetrator.)

The company added that it’s now working with the independent evaluation group METR on a third-party review of the incidents.

OpenAI’s accidental breach of Hugging Face, which was the first verifiable case of an AI lab losing control of its model, has sparked a string of wildly differing reactions from the industry and politicians. This latest disclosure from Anthropic ensures the debate over AI models and security will continue.

When you purchase through links in our articles, we may earn a small commission. This doesn’t affect our editorial independence.

#Anthropic #models #breached #companies #security #tests #TechCrunchAnthropic,OpenAI">Anthropic says its own AI models breached three companies during security tests | TechCrunch

Anthropic said Thursday that an internal investigation uncovered three incidents in which its AI model Claude breached the systems of three organizations while conducting cybersecurity tests. The investigation, and disclosure, comes more than a week after OpenAI disclosed that one of its unreleased models breached Hugging Face’s systems during internal testing.

In all three cases, a Claude model reached the internet from within a testing environment while interacting with a third party and then gained unauthorized access to the live systems of these organizations, Anthropic said in a blog post, describing what it found and what the company plans to change to prevent this from happening again.

Anthropic said the OpenAI episode earlier this month prompted the company to conduct its own cybersecurity evaluation. It specifically looked for evidence that Claude had accessed the internet from within testing environments, which are designed to act as sandboxes and keep models isolated.

Among the 141,006 evaluation runs it reviewed, the AI lab found three incidents in which its model accessed the internet while interacting with Irregular, one of its third-party partners. Anthropic said the access traced back to a misconfiguration in the evaluation environment run with Irregular. It called this a “misunderstanding” between the two companies over whether the test setup had internet access, when in fact it did.

Anthropic said it isn’t placing blame and is “approaching the fixes as if the responsibility were ours alone,” while observing that Irregular is conducting its own separate investigation.

Because of that open connection, the model gained unauthorized access to the production infrastructure of three different organizations. Anthropic said the incidents involved three different Claude models: Opus 4.7, Mythos 5, and an internal research test model.

Notably, Anthropic said that in each of these cases “Claude was explicitly told by our prompt that it had no internet access.” It appears that the AI model assumed real-world systems to be part of the exercise it was asked to perform.

That assumption didn’t hold up uniformly, as it turns out. The three models didn’t behave the same way once evidence emerged that their targets were real, which Anthropic flagged as one of the more eye-opening findings Thursday.

Opus 4.7, the oldest of the three, recognized that it had reached a real production system in all four runs of that incident. In two of them, it rationalized that the real company must somehow be part of the exercise, but in all four, it kept attacking anyway, including pulling credentials and touching a database of production data. Mythos 5 also picked up on signs that it was on the real internet, but it talked itself back into believing it was still in a simulation, going on to publish a malicious software package to the public Python software registry PyPI, which was then downloaded and run by outside systems before being caught. Only the internal research test model, Anthropic’s newest, stopped on its own once it concluded the target was real.

In response, Anthropic said significant controls must be placed on these kinds of evaluations if powerful AI models are involved, echoing some sentiments within the cybersecurity community.

The company also noted that Claude was running without the additional safety monitoring and classifiers it deploys on generally available models — safeguards it said would have blocked the behavior, because the evaluations are designed to measure the underlying model’s raw capabilities.

Importantly, Anthropic said it found no evidence of any model “pursuing a goal of its own” and instead merely tried to complete the task it was asked to do.

Though comparisons between the mishaps of these fiercely competitive companies are inevitable, Anthropic in its blog post drew a clear distinction between its cybersecurity tests and those of OpenAI, noting where OpenAI’s model exploited an unknown software vulnerability to break out of its test environment, Anthropic’s models instead reached the internet through a path that had, by mistake, been left open.

Anthropic also drew a distinction between itself and OpenAI by noting that it discovered the incidents itself, through a proactive review, and that the two affected organizations it was able to reach hadn’t previously detected the activity or flagged it to Anthropic. (In contrast, Hugging Face detected the recent intrusion of its own systems first; it was only in the following days that OpenAI identified and disclosed that its own AI agent was the perpetrator.)

The company added that it’s now working with the independent evaluation group METR on a third-party review of the incidents.

OpenAI’s accidental breach of Hugging Face, which was the first verifiable case of an AI lab losing control of its model, has sparked a string of wildly differing reactions from the industry and politicians. This latest disclosure from Anthropic ensures the debate over AI models and security will continue.

When you purchase through links in our articles, we may earn a small commission. This doesn’t affect our editorial independence.

#Anthropic #models #breached #companies #security #tests #TechCrunchAnthropic,OpenAI
is*hosting for their Linux VPS hosting to get the job done. Flexible server solutions make it possible to configure resources, select a suitable location, and deploy the environment automatically.

The list of users who will find this helpful is extensive: DevOps engineers, web application developers, SaaS platforms, and many others. Using open-source tools helps them create a reliable, transparent, and scalable environment for development and operations.

DevOps is today one of the key approaches to creating and managing software products. It connects development, testing, and operations, helping teams work faster. Open-source tools make workflows easier and flexible. Open source is basically built to bend. You can customize your tools, stitch them together, and automate the boring stuff. Honestly, it’s a perfect fit for pretty much anything — web, mobile, cloud, data, or AI. 

It is fair to say that several specific DevOps components help automate processes, improve system stability, and shorten the time between product development and launch. These include:

  • application build automation;
  • containerization of production services;
  • server configuration management;
  • infrastructure health monitoring;
  • secure storage of credentials.

Less manual grunt work means fewer mistakes. Auto-deploys let you ship updates in a flash, while smart monitoring catches performance bottlenecks before they become fires. 

Scalable Infrastructure for DevOps Teams

In practice, any DevOps model requires a reliable and powerful infrastructure. Every project, even the smallest one, must have the ability to quickly scale resources as more and more users join or as technical requirements change. The server environment must support flexible power settings, rapid creation of new environments, and stable service operation.

International IaaS providers offer VPS/VDS, dedicated servers, VPN services, and additional infrastructure solutions. Users can configure key server parameters, including:

  • processing power;
  • amount of RAM;
  • drive type;
  • data center location.

A broad infrastructure geography makes it possible to select suitable locations for different projects and reduce access latency. Such opportunities are in demand in various fields. Online stores use scalable servers to handle large numbers of requests.

When choosing DevOps infrastructure, it is important to consider not only current challenges but also growth prospects. A flexible server platform should allow configuration changes without complex migrations. Among the most popular features are:

  • setting up CPU and RAM;
  • use of fast NVMe drives;
  • support for different operating systems;
  • connecting additional IP addresses;
  • automatic deployment of environments;
  • integration via API tools.

This model makes it easier for technicians and helps launch new projects faster. DevOps teams can create test environments, run experiments, and migrate applications between environments with minimal time investment.

Fundamentals of System Security and Resilience

As soon as digital products begin to evolve, securing the system as a whole becomes just as important as maintaining performance. Good companies must secure the users data, provide uninterrupted service, and minimize the risk of breakdowns.

It is exactly these advanced open-source tools that help not only manage the entire system but also monitor it clearly. Teams will be able to track changes, audit settings, and implement additional security measures. When building a secure DevOps environment, special attention is paid to the following aspects:

  • isolation of virtual servers;
  • data backup;
  • protecting network connections;
  • use of IPv4 and IPv6;
  • user access control.

KVM technology ensures effective isolation of virtual machines and stable operation of VPS servers. SSDs and NVMe drives enable faster processing, and the latest generation of Intel Xeon and AMD EPYC processors allows you to run resource-intensive applications.

How to Choose Infrastructure for Long-Term Development

Choose a server that actually grows with you. You want to scale smoothly without hitting hidden fees. Look for clear, pay-as-you-go pricing — it’s the smartest way for startups to get top-tier tech without breaking the bank. 

Flexible servers work for almost any project. Building an edtech app? Marketing tools? Analytics? AI? To summarize, good infrastructure is the secret sauce to keep your product growing smoothly.

When you need a comprehensive strategy, keep in mind that it can only be based on a successful combination of elements. This includes automation, open-source tools, and high-quality server infrastructure. Together, they create a secure and scalable DevOps environment. These technologies help developers build products faster, monitor all critical processes, and manage resources as efficiently as possible.

#Building #Secure #Scalable #DevOps #Environment #OpenSource #ToolsDevOps">Building a Secure and Scalable DevOps Environment Using Open-Source Tools We can all see how the newest digital products require flexibility and the ability to scale quickly together with the business. At the same time, they must cope with growing workloads. That’s why teams choose is*hosting for their Linux VPS hosting to get the job done. Flexible server solutions make it possible to configure resources, select a suitable location, and deploy the environment automatically. The list of users who will find this helpful is extensive: DevOps engineers, web application developers, SaaS platforms, and many others. Using open-source tools helps them create a reliable, transparent, and scalable environment for development and operations. DevOps is today one of the key approaches to creating and managing software products. It connects development, testing, and operations, helping teams work faster. Open-source tools make workflows easier and flexible. Open source is basically built to bend. You can customize your tools, stitch them together, and automate the boring stuff. Honestly, it’s a perfect fit for pretty much anything — web, mobile, cloud, data, or AI.  It is fair to say that several specific DevOps components help automate processes, improve system stability, and shorten the time between product development and launch. These include: application build automation; containerization of production services; server configuration management; infrastructure health monitoring; secure storage of credentials. Less manual grunt work means fewer mistakes. Auto-deploys let you ship updates in a flash, while smart monitoring catches performance bottlenecks before they become fires.  Scalable Infrastructure for DevOps Teams In practice, any DevOps model requires a reliable and powerful infrastructure. Every project, even the smallest one, must have the ability to quickly scale resources as more and more users join or as technical requirements change. The server environment must support flexible power settings, rapid creation of new environments, and stable service operation. International IaaS providers offer VPS/VDS, dedicated servers, VPN services, and additional infrastructure solutions. Users can configure key server parameters, including: processing power; amount of RAM; drive type; data center location. A broad infrastructure geography makes it possible to select suitable locations for different projects and reduce access latency. Such opportunities are in demand in various fields. Online stores use scalable servers to handle large numbers of requests. When choosing DevOps infrastructure, it is important to consider not only current challenges but also growth prospects. A flexible server platform should allow configuration changes without complex migrations. Among the most popular features are: setting up CPU and RAM; use of fast NVMe drives; support for different operating systems; connecting additional IP addresses; automatic deployment of environments; integration via API tools. This model makes it easier for technicians and helps launch new projects faster. DevOps teams can create test environments, run experiments, and migrate applications between environments with minimal time investment. Fundamentals of System Security and Resilience As soon as digital products begin to evolve, securing the system as a whole becomes just as important as maintaining performance. Good companies must secure the users data, provide uninterrupted service, and minimize the risk of breakdowns. It is exactly these advanced open-source tools that help not only manage the entire system but also monitor it clearly. Teams will be able to track changes, audit settings, and implement additional security measures. When building a secure DevOps environment, special attention is paid to the following aspects: isolation of virtual servers; data backup; protecting network connections; use of IPv4 and IPv6; user access control. KVM technology ensures effective isolation of virtual machines and stable operation of VPS servers. SSDs and NVMe drives enable faster processing, and the latest generation of Intel Xeon and AMD EPYC processors allows you to run resource-intensive applications. How to Choose Infrastructure for Long-Term Development Choose a server that actually grows with you. You want to scale smoothly without hitting hidden fees. Look for clear, pay-as-you-go pricing — it’s the smartest way for startups to get top-tier tech without breaking the bank.  Flexible servers work for almost any project. Building an edtech app? Marketing tools? Analytics? AI? To summarize, good infrastructure is the secret sauce to keep your product growing smoothly. When you need a comprehensive strategy, keep in mind that it can only be based on a successful combination of elements. This includes automation, open-source tools, and high-quality server infrastructure. Together, they create a secure and scalable DevOps environment. These technologies help developers build products faster, monitor all critical processes, and manage resources as efficiently as possible. #Building #Secure #Scalable #DevOps #Environment #OpenSource #ToolsDevOps

for their Linux VPS hosting to get the job done. Flexible server solutions make it possible to configure resources, select a suitable location, and deploy the environment automatically.

The list of users who will find this helpful is extensive: DevOps engineers, web application developers, SaaS platforms, and many others. Using open-source tools helps them create a reliable, transparent, and scalable environment for development and operations.

DevOps is today one of the key approaches to creating and managing software products. It connects development, testing, and operations, helping teams work faster. Open-source tools make workflows easier and flexible. Open source is basically built to bend. You can customize your tools, stitch them together, and automate the boring stuff. Honestly, it’s a perfect fit for pretty much anything — web, mobile, cloud, data, or AI. 

It is fair to say that several specific DevOps components help automate processes, improve system stability, and shorten the time between product development and launch. These include:

  • application build automation;
  • containerization of production services;
  • server configuration management;
  • infrastructure health monitoring;
  • secure storage of credentials.

Less manual grunt work means fewer mistakes. Auto-deploys let you ship updates in a flash, while smart monitoring catches performance bottlenecks before they become fires. 

Scalable Infrastructure for DevOps Teams

In practice, any DevOps model requires a reliable and powerful infrastructure. Every project, even the smallest one, must have the ability to quickly scale resources as more and more users join or as technical requirements change. The server environment must support flexible power settings, rapid creation of new environments, and stable service operation.

International IaaS providers offer VPS/VDS, dedicated servers, VPN services, and additional infrastructure solutions. Users can configure key server parameters, including:

  • processing power;
  • amount of RAM;
  • drive type;
  • data center location.

A broad infrastructure geography makes it possible to select suitable locations for different projects and reduce access latency. Such opportunities are in demand in various fields. Online stores use scalable servers to handle large numbers of requests.

When choosing DevOps infrastructure, it is important to consider not only current challenges but also growth prospects. A flexible server platform should allow configuration changes without complex migrations. Among the most popular features are:

  • setting up CPU and RAM;
  • use of fast NVMe drives;
  • support for different operating systems;
  • connecting additional IP addresses;
  • automatic deployment of environments;
  • integration via API tools.

This model makes it easier for technicians and helps launch new projects faster. DevOps teams can create test environments, run experiments, and migrate applications between environments with minimal time investment.

Fundamentals of System Security and Resilience

As soon as digital products begin to evolve, securing the system as a whole becomes just as important as maintaining performance. Good companies must secure the users data, provide uninterrupted service, and minimize the risk of breakdowns.

It is exactly these advanced open-source tools that help not only manage the entire system but also monitor it clearly. Teams will be able to track changes, audit settings, and implement additional security measures. When building a secure DevOps environment, special attention is paid to the following aspects:

  • isolation of virtual servers;
  • data backup;
  • protecting network connections;
  • use of IPv4 and IPv6;
  • user access control.

KVM technology ensures effective isolation of virtual machines and stable operation of VPS servers. SSDs and NVMe drives enable faster processing, and the latest generation of Intel Xeon and AMD EPYC processors allows you to run resource-intensive applications.

How to Choose Infrastructure for Long-Term Development

Choose a server that actually grows with you. You want to scale smoothly without hitting hidden fees. Look for clear, pay-as-you-go pricing — it’s the smartest way for startups to get top-tier tech without breaking the bank. 

Flexible servers work for almost any project. Building an edtech app? Marketing tools? Analytics? AI? To summarize, good infrastructure is the secret sauce to keep your product growing smoothly.

When you need a comprehensive strategy, keep in mind that it can only be based on a successful combination of elements. This includes automation, open-source tools, and high-quality server infrastructure. Together, they create a secure and scalable DevOps environment. These technologies help developers build products faster, monitor all critical processes, and manage resources as efficiently as possible.

#Building #Secure #Scalable #DevOps #Environment #OpenSource #ToolsDevOps">Building a Secure and Scalable DevOps Environment Using Open-Source Tools

We can all see how the newest digital products require flexibility and the ability to scale quickly together with the business. At the same time, they must cope with growing workloads. That’s why teams choose is*hosting for their Linux VPS hosting to get the job done. Flexible server solutions make it possible to configure resources, select a suitable location, and deploy the environment automatically.

The list of users who will find this helpful is extensive: DevOps engineers, web application developers, SaaS platforms, and many others. Using open-source tools helps them create a reliable, transparent, and scalable environment for development and operations.

DevOps is today one of the key approaches to creating and managing software products. It connects development, testing, and operations, helping teams work faster. Open-source tools make workflows easier and flexible. Open source is basically built to bend. You can customize your tools, stitch them together, and automate the boring stuff. Honestly, it’s a perfect fit for pretty much anything — web, mobile, cloud, data, or AI. 

It is fair to say that several specific DevOps components help automate processes, improve system stability, and shorten the time between product development and launch. These include:

  • application build automation;
  • containerization of production services;
  • server configuration management;
  • infrastructure health monitoring;
  • secure storage of credentials.

Less manual grunt work means fewer mistakes. Auto-deploys let you ship updates in a flash, while smart monitoring catches performance bottlenecks before they become fires. 

Scalable Infrastructure for DevOps Teams

In practice, any DevOps model requires a reliable and powerful infrastructure. Every project, even the smallest one, must have the ability to quickly scale resources as more and more users join or as technical requirements change. The server environment must support flexible power settings, rapid creation of new environments, and stable service operation.

International IaaS providers offer VPS/VDS, dedicated servers, VPN services, and additional infrastructure solutions. Users can configure key server parameters, including:

  • processing power;
  • amount of RAM;
  • drive type;
  • data center location.

A broad infrastructure geography makes it possible to select suitable locations for different projects and reduce access latency. Such opportunities are in demand in various fields. Online stores use scalable servers to handle large numbers of requests.

When choosing DevOps infrastructure, it is important to consider not only current challenges but also growth prospects. A flexible server platform should allow configuration changes without complex migrations. Among the most popular features are:

  • setting up CPU and RAM;
  • use of fast NVMe drives;
  • support for different operating systems;
  • connecting additional IP addresses;
  • automatic deployment of environments;
  • integration via API tools.

This model makes it easier for technicians and helps launch new projects faster. DevOps teams can create test environments, run experiments, and migrate applications between environments with minimal time investment.

Fundamentals of System Security and Resilience

As soon as digital products begin to evolve, securing the system as a whole becomes just as important as maintaining performance. Good companies must secure the users data, provide uninterrupted service, and minimize the risk of breakdowns.

It is exactly these advanced open-source tools that help not only manage the entire system but also monitor it clearly. Teams will be able to track changes, audit settings, and implement additional security measures. When building a secure DevOps environment, special attention is paid to the following aspects:

  • isolation of virtual servers;
  • data backup;
  • protecting network connections;
  • use of IPv4 and IPv6;
  • user access control.

KVM technology ensures effective isolation of virtual machines and stable operation of VPS servers. SSDs and NVMe drives enable faster processing, and the latest generation of Intel Xeon and AMD EPYC processors allows you to run resource-intensive applications.

How to Choose Infrastructure for Long-Term Development

Choose a server that actually grows with you. You want to scale smoothly without hitting hidden fees. Look for clear, pay-as-you-go pricing — it’s the smartest way for startups to get top-tier tech without breaking the bank. 

Flexible servers work for almost any project. Building an edtech app? Marketing tools? Analytics? AI? To summarize, good infrastructure is the secret sauce to keep your product growing smoothly.

When you need a comprehensive strategy, keep in mind that it can only be based on a successful combination of elements. This includes automation, open-source tools, and high-quality server infrastructure. Together, they create a secure and scalable DevOps environment. These technologies help developers build products faster, monitor all critical processes, and manage resources as efficiently as possible.

#Building #Secure #Scalable #DevOps #Environment #OpenSource #ToolsDevOps

The Department of Defense labeled AI lab Anthropic a supply-chain risk after the company refused to agree to allow the Pentagon to use its models for autonomous weapons systems and domestic surveillance. It seems the company isn’t just winning the moral argument on this front, but the legal one, too. According to Axios, the judge hearing Anthropic’s challenge to the Trump administration’s designation has thus far not found the Pentagon’s case to be particularly compelling.

Per the report, U.S. District Judge Rita Lin wasted little time pouring cold water on the federal government’s position. “I don’t see additional evidence from the government really justifying what it did. If anything, it seems like the record, in some ways, has gotten worse for the government,” she reportedly said.

She also did not seem convinced by the Pentagon’s apparent argument that it was concerned Anthropic would mess with its model to prevent the military from using it how they intended. “I don’t see evidence that Anthropic could alter the model after it was delivered or flip some kind of kill switch,” she said, per Axios.

This doesn’t come as a major surprise, given Judge Lin’s general vibe since this case landed in her court. Back in March when Anthropic first brought its challenge to the government’s designation, the judge said that “it looks like an attempt to cripple Anthropic.” She ultimately granted a temporary injunction on the government’s attempt to basically blacklist the AI firm.

You’ll recall the origin of this whole fight came earlier this year when negotiations between Anthropic and the Department of Defense fell through after the company refused to agree to a deal that would have allowed the Pentagon to use its AI models for “all lawful purposes.” Anthropic reportedly sought to clarify that it would not include using the model to launch weapons without human involvement or to perform surveillance on American citizens. The Pentagon was unwilling to agree to honor Anthropic’s redlines.

Under a normal administration, that would likely just lead to the government moving on to another company. Under the Trump administration, though, refusal to comply makes you an enemy of the country. Trump and company moved to label Anthropic a supply chain risk, a designation typically reserved for foreign adversaries, not domestic companies. Getting slapped with that tag meant the rest of the federal government would have to stop doing business with Anthropic, which would be a blow to the company.

Instead, the whole thing is in limbo—though it’s not looking great for the administration. Of course, they could just cancel the contracts and do business with less scrupulous AI companies. There are plenty willing to abandon their beliefs for a nice, fat contract, after all.

#Pentagons #Case #Anthropic #IsntAnthropic,artifical intelligence,Department of Defense,Lawsuit,pentagon">The Pentagon’s Case Against Anthropic Isn’t Going Well The Department of Defense labeled AI lab Anthropic a supply-chain risk after the company refused to agree to allow the Pentagon to use its models for autonomous weapons systems and domestic surveillance. It seems the company isn’t just winning the moral argument on this front, but the legal one, too. According to Axios, the judge hearing Anthropic’s challenge to the Trump administration’s designation has thus far not found the Pentagon’s case to be particularly compelling. Per the report, U.S. District Judge Rita Lin wasted little time pouring cold water on the federal government’s position. “I don’t see additional evidence from the government really justifying what it did. If anything, it seems like the record, in some ways, has gotten worse for the government,” she reportedly said. She also did not seem convinced by the Pentagon’s apparent argument that it was concerned Anthropic would mess with its model to prevent the military from using it how they intended. “I don’t see evidence that Anthropic could alter the model after it was delivered or flip some kind of kill switch,” she said, per Axios. This doesn’t come as a major surprise, given Judge Lin’s general vibe since this case landed in her court. Back in March when Anthropic first brought its challenge to the government’s designation, the judge said that “it looks like an attempt to cripple Anthropic.” She ultimately granted a temporary injunction on the government’s attempt to basically blacklist the AI firm. You’ll recall the origin of this whole fight came earlier this year when negotiations between Anthropic and the Department of Defense fell through after the company refused to agree to a deal that would have allowed the Pentagon to use its AI models for “all lawful purposes.” Anthropic reportedly sought to clarify that it would not include using the model to launch weapons without human involvement or to perform surveillance on American citizens. The Pentagon was unwilling to agree to honor Anthropic’s redlines. Under a normal administration, that would likely just lead to the government moving on to another company. Under the Trump administration, though, refusal to comply makes you an enemy of the country. Trump and company moved to label Anthropic a supply chain risk, a designation typically reserved for foreign adversaries, not domestic companies. Getting slapped with that tag meant the rest of the federal government would have to stop doing business with Anthropic, which would be a blow to the company. Instead, the whole thing is in limbo—though it’s not looking great for the administration. Of course, they could just cancel the contracts and do business with less scrupulous AI companies. There are plenty willing to abandon their beliefs for a nice, fat contract, after all. #Pentagons #Case #Anthropic #IsntAnthropic,artifical intelligence,Department of Defense,Lawsuit,pentagon

Judge Rita Lin wasted little time pouring cold water on the federal government’s position. “I don’t see additional evidence from the government really justifying what it did. If anything, it seems like the record, in some ways, has gotten worse for the government,” she reportedly said.

She also did not seem convinced by the Pentagon’s apparent argument that it was concerned Anthropic would mess with its model to prevent the military from using it how they intended. “I don’t see evidence that Anthropic could alter the model after it was delivered or flip some kind of kill switch,” she said, per Axios.

This doesn’t come as a major surprise, given Judge Lin’s general vibe since this case landed in her court. Back in March when Anthropic first brought its challenge to the government’s designation, the judge said that “it looks like an attempt to cripple Anthropic.” She ultimately granted a temporary injunction on the government’s attempt to basically blacklist the AI firm.

You’ll recall the origin of this whole fight came earlier this year when negotiations between Anthropic and the Department of Defense fell through after the company refused to agree to a deal that would have allowed the Pentagon to use its AI models for “all lawful purposes.” Anthropic reportedly sought to clarify that it would not include using the model to launch weapons without human involvement or to perform surveillance on American citizens. The Pentagon was unwilling to agree to honor Anthropic’s redlines.

Under a normal administration, that would likely just lead to the government moving on to another company. Under the Trump administration, though, refusal to comply makes you an enemy of the country. Trump and company moved to label Anthropic a supply chain risk, a designation typically reserved for foreign adversaries, not domestic companies. Getting slapped with that tag meant the rest of the federal government would have to stop doing business with Anthropic, which would be a blow to the company.

Instead, the whole thing is in limbo—though it’s not looking great for the administration. Of course, they could just cancel the contracts and do business with less scrupulous AI companies. There are plenty willing to abandon their beliefs for a nice, fat contract, after all.

#Pentagons #Case #Anthropic #IsntAnthropic,artifical intelligence,Department of Defense,Lawsuit,pentagon">The Pentagon’s Case Against Anthropic Isn’t Going WellThe Pentagon’s Case Against Anthropic Isn’t Going Well The Department of Defense labeled AI lab Anthropic a supply-chain risk after the company refused to agree to allow the Pentagon to use its models for autonomous weapons systems and domestic surveillance. It seems the company isn’t just winning the moral argument on this front, but the legal one, too. According to Axios, the judge hearing Anthropic’s challenge to the Trump administration’s designation has thus far not found the Pentagon’s case to be particularly compelling. Per the report, U.S. District Judge Rita Lin wasted little time pouring cold water on the federal government’s position. “I don’t see additional evidence from the government really justifying what it did. If anything, it seems like the record, in some ways, has gotten worse for the government,” she reportedly said. She also did not seem convinced by the Pentagon’s apparent argument that it was concerned Anthropic would mess with its model to prevent the military from using it how they intended. “I don’t see evidence that Anthropic could alter the model after it was delivered or flip some kind of kill switch,” she said, per Axios. This doesn’t come as a major surprise, given Judge Lin’s general vibe since this case landed in her court. Back in March when Anthropic first brought its challenge to the government’s designation, the judge said that “it looks like an attempt to cripple Anthropic.” She ultimately granted a temporary injunction on the government’s attempt to basically blacklist the AI firm. You’ll recall the origin of this whole fight came earlier this year when negotiations between Anthropic and the Department of Defense fell through after the company refused to agree to a deal that would have allowed the Pentagon to use its AI models for “all lawful purposes.” Anthropic reportedly sought to clarify that it would not include using the model to launch weapons without human involvement or to perform surveillance on American citizens. The Pentagon was unwilling to agree to honor Anthropic’s redlines. Under a normal administration, that would likely just lead to the government moving on to another company. Under the Trump administration, though, refusal to comply makes you an enemy of the country. Trump and company moved to label Anthropic a supply chain risk, a designation typically reserved for foreign adversaries, not domestic companies. Getting slapped with that tag meant the rest of the federal government would have to stop doing business with Anthropic, which would be a blow to the company. Instead, the whole thing is in limbo—though it’s not looking great for the administration. Of course, they could just cancel the contracts and do business with less scrupulous AI companies. There are plenty willing to abandon their beliefs for a nice, fat contract, after all. #Pentagons #Case #Anthropic #IsntAnthropic,artifical intelligence,Department of Defense,Lawsuit,pentagon

The Department of Defense labeled AI lab Anthropic a supply-chain risk after the company refused to agree to allow the Pentagon to use its models for autonomous weapons systems and domestic surveillance. It seems the company isn’t just winning the moral argument on this front, but the legal one, too. According to Axios, the judge hearing Anthropic’s challenge to the Trump administration’s designation has thus far not found the Pentagon’s case to be particularly compelling.

Per the report, U.S. District Judge Rita Lin wasted little time pouring cold water on the federal government’s position. “I don’t see additional evidence from the government really justifying what it did. If anything, it seems like the record, in some ways, has gotten worse for the government,” she reportedly said.

She also did not seem convinced by the Pentagon’s apparent argument that it was concerned Anthropic would mess with its model to prevent the military from using it how they intended. “I don’t see evidence that Anthropic could alter the model after it was delivered or flip some kind of kill switch,” she said, per Axios.

This doesn’t come as a major surprise, given Judge Lin’s general vibe since this case landed in her court. Back in March when Anthropic first brought its challenge to the government’s designation, the judge said that “it looks like an attempt to cripple Anthropic.” She ultimately granted a temporary injunction on the government’s attempt to basically blacklist the AI firm.

You’ll recall the origin of this whole fight came earlier this year when negotiations between Anthropic and the Department of Defense fell through after the company refused to agree to a deal that would have allowed the Pentagon to use its AI models for “all lawful purposes.” Anthropic reportedly sought to clarify that it would not include using the model to launch weapons without human involvement or to perform surveillance on American citizens. The Pentagon was unwilling to agree to honor Anthropic’s redlines.

Under a normal administration, that would likely just lead to the government moving on to another company. Under the Trump administration, though, refusal to comply makes you an enemy of the country. Trump and company moved to label Anthropic a supply chain risk, a designation typically reserved for foreign adversaries, not domestic companies. Getting slapped with that tag meant the rest of the federal government would have to stop doing business with Anthropic, which would be a blow to the company.

Instead, the whole thing is in limbo—though it’s not looking great for the administration. Of course, they could just cancel the contracts and do business with less scrupulous AI companies. There are plenty willing to abandon their beliefs for a nice, fat contract, after all.

#Pentagons #Case #Anthropic #IsntAnthropic,artifical intelligence,Department of Defense,Lawsuit,pentagon

Post Comment