TL;DR
Roblox launched Build, a mobile-first AI creation tab that generates games from text prompts, starting alpha in New Zealand on July 28.
Hundreds of cities across the US had adopted a now-familiar brand: Flock Safety surveillance systems, using controversial, AI license plate detection cameras and broad contracts with local police. Now cities, from my home of Bend, Oregon, to the LAPD in Los Angeles, are canceling their Flock contracts, while other towns are even covering Flock cameras with plastic bags while trying to figure out if the cams are actually shut down.
So, what does it mean when you spot the first camera-and-solar-panel Flock setup in your own neighborhood? I talked to Flock, the American Civil Liberties Union and others about what you need to know.
Read more: State Laws Against Surveillance and License Plate Cams
Flock made headlines late last year during widespread crackdowns by US Immigration and Customs Enforcement. Though Flock doesn’t have a direct partnership with federal agencies (a blurry line I’ll discuss below), law enforcement agencies are free to share data with departments like ICE, and they frequently do. And Flock Safety coverage, along with citizen concerns, has only risen since then.
One study from the Center for Human Rights at the University of Washington found that at least eight Washington law enforcement agencies shared their Flock data networks directly with ICE in 2025, and 10 more departments allowed ICE backdoor access without explicitly granting the agency permission. Many other reports outline similar activity.
Following Super Bowl ads about finding lost dogs, Flock was under scrutiny about its planned partnership with Ring, Amazon’s security brand. The integration would have allowed police to request the use of Ring-brand home security cameras for investigations. Following intense public backlash, Ring cut ties with Flock just like my city did, although it now faces a new lawsuit for its own face recognition systems.
To learn more, I spoke to Flock about how the company’s surveillance technology is used (and misused). I also spoke with privacy advocates from the ACLU to discuss surveillance concerns and what communities are doing about it.
Flock’s presence means license plate cameras — and these days, much more.
If you hear that Flock is setting up near you, it usually means the installation of ALPR cameras to capture license plate photos and monitor cars on the street.
Flock signs contracts with a wide range of entities, including city governments and law enforcement departments. A neighborhood can also partner with Flock — for example, if a homeowners’ association decides it wants extra eyes on the road, it may choose to use Flock’s systems.
When Flock secures a contract, the company installs cameras at strategic locations. Though these cameras are primarily marketed for license plate recognition, Flock reports on its site that its surveillance system is intended to reduce crime, including property crimes such as “mail and package theft, home invasions, vandalism, trespassing and burglary.” The company also says it frequently solves violent crimes like “assault, kidnappings, shootings and homicides.”
Flock has recently expanded into other technologies, including advanced cameras that monitor more than just vehicles. Most concerning are the latest Flock drones equipped with high-powered cameras. Flock’s “Drone as First Responder” platform automates drone operations, including launching them in response to 911 calls or gunfire. Flock’s drones, which reach speeds up to 60 mph, can follow vehicles or people and provide information to law enforcement.
Drones like these can be used to track fleeing suspects. In practice, the key is how law enforcement chooses to use them, and whether states pass laws allowing police to use drones without a warrant — I’ll cover state laws more below, because that’s a big part of today’s surveillance.
It’s important to note that not all cities or neighborhoods refer to Flock Safety by name, even when using its technology. They might mention the Drone as First Responder program, or ALPR cameras, without further details. For example, a March announcement about police drones from the city of Lancaster, California, doesn’t mention Flock at all, even though it was the company behind the drone program.
Flock has expanded from cameras to drones, and with that comes greater ability to track people as well as cars.
Flock states on its website that its standard license-plate cameras cannot technically track vehicles, but only take a “point-in-time” image of a car to nab the license plate.
However, due to AI video and image search, contracted parties like local law enforcement can use these tools to piece together license information and form their own timeline of where and when a vehicle went. Adding to those capabilities, Flock also told Forbes that it’s making efforts to expand access to include video clips and live feeds.
Flock’s machine learning can also note details like a vehicle’s body type, color, the condition of the license plate and a wide variety of identifiers, like roof racks, paint colors and what you have stored in the back. Flock rarely calls this AI, but it’s similar to AI-recognition features you can find in the latest home security cameras
A Flock spokesperson told me the company has boundaries and does not use facial recognition: “We have more traditional video cameras that can send an alert when one sees if a person is in the frame, for instance, in a business park at 2 a.m. or in the public parks after dark.”
By “traditional” cameras, Flock refers to those that capture a wider field of view — more than just cars and license plates — and can record video rather than just snapshot images.
The information Flock can access provides a comprehensive picture that police can use to track cars by running searches on their software. Just like you might Google a local restaurant, police can search for a basic vehicle description and retrieve recent matches that the surveillance equipment may have found. Those searches can sometimes extend to people, too.
“We have an investigative tool called Freeform that lets you use natural language prompts to find the investigative lead you’re looking for, including the description of what a person’s clothes may be,” the Flock spokesperson told me.
Unlike red-light cameras, Flock’s cameras can be installed nearly anywhere and snap vehicle ID images for all cars. There are Safe Lists that people can use to help Flock cameras filter out vehicles by filling out a form with their address and license plate to mark their vehicle as a “resident.”
The opposite is also true: Flock cameras can use a hot list of known, wanted vehicles and send automatic alerts to police if one is found.
With Flock drones, these intelligent searches become even more complete, allowing cameras to track where cars are going and identify people. That raises additional privacy concerns about having eyes in the sky over your backyard.
“While flying, the drone faces forward, looking at the horizon, until it gets to the call for service, at which point the camera looks down,” the Flock spokesperson said. “Every flight path is logged in a publicly available flight dashboard for appropriate oversight.”
Yet unlike personal security options, there’s no easy way to opt out of this kind of surveillance. You can’t turn off a feature, cancel a subscription or throw away a device to avoid it.
And even though more than 45 cities have canceled Flock contracts amid public outcry, that doesn’t guarantee that all surveillance cameras will be removed from the designated area.
When I reached out to the police department in Eugene, another city in Oregon that ended its Flock contract, the PD director of public information told me that, while there were concerns about certain vulnerabilities and data security requirements with the particular vendor, the technology itself is not the problem. “Eugene Police’s ALPR system experience has demonstrated the value of leveraging ALPR technology to aid investigations … the department must ensure that any vendors meet the highest standards.”
License plates can be closely connected to your personal information.
Flock’s stance, as outlined in its privacy and ethics guide, is that license plate numbers and vehicle descriptions aren’t personal information. The company says it doesn’t surveil “private data” — only cars and general descriptive markers.
But vehicle information can be considered personal because it’s legally tied to the vehicle’s owner. Privacy laws, including proposed federal legislation from 2026, prohibit the release of personal information from state motor vehicle records in order to protect citizens.
However, those laws typically include exemptions for legal actions and law enforcement, sometimes even for private security companies.
AI detection also plays a role. When someone can identify a vehicle through searches like “red pickup truck with a dog in the bed,” that tracking goes beyond basic license plates to much more personal information about the driver and their life. It may include the bumper stickers, what can be seen in the backseat and whether a vehicle has a visible gun rack.
Flock’s practices — like its recent push toward live video feeds and drones to track suspects — move out of the gray area, and that’s where privacy advocates are rightly concerned. Despite its policy, it appears you can track specific people using Flock tech. You’ll just need to pay more to do so, such as upgrading from ALPRs to Flock’s suspect-following drone program, or using its Freeform tool to track someone by the clothes they’re wearing.
Flock’s security practices are solid, but it’s the company’s users I’m worried about.
Flock states on its website that it stores data for 30 days on Amazon Web Services cloud storage and then deletes it. It uses KMS-based encryption (a managed encryption key system common in AWS) and reports that all images and related data are encrypted from on-device storage to cloud storage.
When Flock collects criminal justice information, or sensitive data managed by law enforcement, it’s only available to official government agencies, not an entity like your local HOA. Because video data is encrypted throughout its transfer to the end user, employees at Flock cannot access it. These are the same kind of security practices I look for when reviewing home security cameras, but there are more complications here.
However, Flock also makes it clear that its customers — whether that’s a local police department, private business or another institution — own their data and control access to it. Once end users access that data, Flock’s own privacy measures don’t do much to help. That raises concerns about the security of local law enforcement systems, each of which has its own data regulations and accountability practices.
Flock can audit camera access, but that hasn’t prevented bad behaviors so far.
You may have noticed a theme: Flock provides powerful surveillance technology, and the final results are deeply influenced by how customers use it. That can be creepy at best, and an illegal abuse of power at worst.
Since Flock Safety began partnering with law enforcement, a growing number of officers have been found abusing the surveillance system. In one instance, a Kansas police chief used Flock cameras 164 times while tracking an ex. In another case, a sheriff in Texas lied about using Flock to “track a missing person,” but was later found to be investigating a possible abortion. In Georgia, a police chief was arrested for using Flock to stalk and harass citizens. In Virginia, a man sued the city of Norfolk over purported privacy violations and discovered that Flock cameras had been used to track him 526 times, around four times per day.
Those are just a few examples from a long list, giving real substance to worries about a surveillance state and a lack of checks and balances. When I asked Flock how its systems protect against abuse and overreach, a spokesperson referred to its accountability feature, an auditing tool that “records every search that a user of Flock conducts in the system.” Flock used this tool during the Georgia case above, which ultimately led to the arrest of the police chief.
While police search logs are often tracked like this, reports indicate that many authorities start searches with vague terms and cast a wide net using terms like “investigation,” “crime” or a broad immigration term like “deportee” to gain access to as much data as possible. While police can’t avoid Flock’s audit logs, they can use general or discriminatory terms — or skip filling out fields entirely — to evade investigations and hide intent.
Regardless of the auditing tools, the onus is on local organizations to manage investigations, accountability and transparency. That brings me to a particularly impactful current event.
While ICE can’t directly access Flock’s system, they tend to get a lot of help from local law enforcement.
ICE is the elephant in the room in my Flock guide. Does Flock share its surveillance data with federal agencies such as ICE? Yes, the federal government frequently has access to that data, but how it gets access is important.
Flock states on its website that it has not shared data or partnered with ICE or any other Department of Homeland Security officials since terminating its pilot programs in August 2025. Flock says its focus is now on local law enforcement, but that comes with a hands-off approach that doesn’t control what happens to information downstream.
“Flock has no authority to share data on our customers’ behalf, nor the authority to disrupt their law enforcement operations,” the Flock spokesperson told me. “Local police all over the country collaborate with federal agencies for various reasons, with or without Flock technology. “
That collaboration has grown more complex. As Sen. Ron Wyden, a Democrat from Oregon, stated in an open letter to Flock Safety, “local” law enforcement isn’t that local anymore, especially when 75% of Flock’s law enforcement customers have enrolled in the National Lookup Tool, which allows information sharing across the country between all participants.
“Flock has built a dangerous platform in which abuse of surveillance data is almost certain,” Wyden wrote. “The company has adopted a see-no-evil approach of not proactively auditing the searches done by its law enforcement customers because, as the company’s Chief Communications Officer told the press, ‘It is not Flock’s job to police the police.’”
Police department sharing isn’t always easy to track, but 404 Media reported last year that police departments across the country have been creating Flock searches with reasons listed as “immigration,” “ICE,” or “ICE warrant,” among others. Again, since police can put whatever terms they want in these fields — depending on local policies — we don’t know for sure how common it is to look up info for ICE.
Additionally, there’s not always an official process or chain of accountability for sharing this data. In Oregon, reports found that a police department was conducting Flock searches on behalf of ICE and the FBI via a simple email thread.
“When this kind of surveillance power is in malevolent hands — and in the case of ICE, I feel comfortable saying a growing number of Americans view it as a bad actor — these companies are empowering actions the public increasingly finds objectionable,” a lawyer with the ACLU told a Salt Lake City news outlet earlier this year.
With the myriad ways law enforcement shares Flock data with the federal government, it may seem like there’s not much you can do. But one powerful tool is advocating for new laws.
State laws differ drastically when it comes to Flock surveillance, but legislation is on the rise.
In the past two years, a growing number of state laws have been passed or proposed to address Flock Safety, license plate readers and surveillance. Much of this legislation is bipartisan, or has been passed by both traditionally right- and left-leaning states, although some go further than others.
When I contacted the ACLU to learn what legislation is most effective in situations like this, Chad Marlow, senior policy counsel and lead on the ACLU’s advocacy work for Flock and related surveillance, gave several examples.
“I would limit the allowed uses for ALPR,” Marlow told me. “While some uses, like for toll collection and Amber Alerts, with the right guardrails in place, are not particularly problematic, some ALPRs are used to target communities of color and low-income communities for fine/fee enforcement and for minor crime enforcement, which can exacerbate existing policing inequities.”
This type of harmful ALPR targeting is typically used to both oppress minorities and bring in a greater number of fees for local law organizations — problems that existed long before AI recognition cameras, but have been exacerbated by the technology.
New legislation can help, but it needs to be carefully crafted. The most effective laws fall into two categories. The first is requiring any collected ALPR or related data to be deleted within a certain time frame — the shorter, the better. New Hampshire wins here with a 3-minute rule.
“For states that want a little more time to see if captured ALPR data is relevant to an ongoing investigation, keeping the data for a few days is sufficient,” Marlow said. “Some states, like Washington and Virginia, recently adopted 21-day limits, which is the very outermost acceptable limit.”
The second type of promising law makes it illegal to share ALPR and similar data outside the state (such as with ICE) and has been passed by states like Virginia, Illinois and California.
“Ideally, no data should be shared outside the collecting agency without a warrant,” Marlow said. “But some states have chosen to prohibit data sharing outside of the state, which is better than nothing, and does limit some risks.”
Vermont, meanwhile, requires a strict approval process for ALPRs that, by 2025, left no law enforcement agency in the state using license cams.
But what happens if police choose to ignore laws and continue using Flock as they see fit? That’s already happened. In California, for example, police in Los Angeles and San Diego were found sharing information with Homeland Security in 2025, in violation of a state law that bans organizations from sharing license plate data out of state.
When this happens, the recourse is typically a lawsuit, either from the state attorney general or a class action by the community, both of which are ongoing in California in 2026. But what should people do while legislation and lawsuits proceed?
Many other AI surveillance tools are appearing, including some aimed at law enforcement and businesses.
Marlow acknowledged that individuals can’t do much about Flock surveillance without bans or legislation.
“Flock identifies and tracks your vehicle by scanning its license plate, and covering your license plate is illegal, so that is not an option,” he told me.
However, Marlow suggested minor changes that could make a difference for those who are seriously worried. “When people are traveling to sensitive locations, they could take public transportation and pay with cash (credit cards can be tracked, as can share-a-rides) or get a lift from a friend, but those aren’t really practical on an everyday basis.”
Ditching or restricting Flock Safety is one way communities are fighting back against what they consider to be unnecessary surveillance with the potential for abuse. But AI surveillance doesn’t begin or end with one company.
When multiple companies, including Motorola, are offering similar tools, the problem becomes much larger than Flock Safety tech.
Flock Safety is an intermediary that provides technology in demand by powerful organizations. It’s hardly the only one with these kinds of high-tech eyes — it’s just one of the first to enter the market at a national level. If Flock were gone, another company would likely step in to fill the gap, unless restricted by law.
As Flock’s integration with other apps and cameras becomes more complex, it’s going to be harder to tell where Flock ends and another solution begins, even without rival companies showing up with the latest AI tracking.
But rivals are showing up, from Shield AI for military intelligence to commercial applications by companies like Ambient.ai, Verkada’s AI security searches and the notorious intelligence firm Palantir, all looking for ways to integrate and expand. Motorola, in particular, is in on the action with its VehicleManager platform.
If you want to take an extra step, you can volunteer, donate and participate in a variety of anti-surveillance activities.
The first step is being aware, including knowing which new cameras your city is installing and which software partnerships your local law enforcement has. If you don’t like what you discover, find ways to participate in the decision-making process, like attending open city council meetings on Flock, as in Bend.
On a broader level, keep track of the legislation your state is considering regarding Flock and similar surveillance contracts and operations, as these will have the greatest long-term impact. Blocking data from being shared out of state and requiring police to delete surveillance ASAP are particularly important steps. You can contact your state senators and representatives to encourage legislation like this.
When you’re wondering what to share with politicians, I recommend something like what Marlow told me: “The idea of keeping a location dossier on every single person just in case one of us turns out to be a criminal is just about the most un-American approach to privacy I can imagine.”
You can also sign up for and donate to projects that are addressing Flock concerns, such as The Plate Privacy Project from The Institute for Justice. I’m currently talking to them about the latest events, and I’ll update if they have any additional tips for us.
Keep following CNET home security, where I break down the latest news you should know, like privacy settings to turn on, security camera settings you may want to turn off and how surveillance intersects with our daily lives. Things are changing fast, but we’re staying on top of it.
Roblox launched Build, a mobile-first AI creation tab that generates games from text prompts, starting alpha in New Zealand on July 28.
Roblox announced Build on Wednesday, a new creation tab inside the Roblox mobile app that lets anyone turn a text prompt into a basic playable game without touching Roblox Studio or writing a line of code. A creator can describe something like a cozy forest adventure game with environmental obstacles, and Build will generate a starting point with gameplay mechanics, environment, characters, sound, and visual style. The feature begins public alpha testing in New Zealand on July 28 for age-verified users nine and older.
Build shares a back end with Roblox Studio, meaning creators can start a project on their phone and continue refining it on desktop with the full Studio toolset, or launch agents from Studio and check progress from mobile. The system is powered by a mix of open-source and proprietary Roblox AI models trained on what the company describes as a uniquely large set of 3D models and gaming-specific data. Roblox’s Cube foundation model, which the company introduced earlier this year alongside agentic Studio tools, generates game-ready objects that can drive, shoot, or otherwise behave as expected without manual scripting.
Roblox said it is aware of the quality risk that comes with lowering the barrier to game creation. The company said its discovery system ranks games by long-term retention, not recency or volume, and that games nobody plays will not surface on the homepage regardless of how they were made. Published games from Build will go through the same safety checks and retention-based discovery ranking as all other Roblox titles, and games targeting younger players will undergo an extended review before being added to the Roblox Kids or Select catalogues.
Alongside Build, Roblox is shipping a suite of agentic tools for professional creators over the coming months. These include a playtesting agent that finds bugs before players encounter them, an analytics agent that answers questions about game performance in plain language, and an experiment agent that identifies tests to improve engagement and monetisation. A new scene-generation model is also in development that will create entire editable and playable 3D environments from a single text prompt.
The announcement comes as AI-generated content is flooding platforms faster than review systems can handle it, a dynamic that drove an 84 percent jump in App Store submissions and prompted Apple to crack down on low-quality AI-built apps. Roblox is betting that its retention-based discovery system will serve as a natural quality filter, surfacing only games that players actually want to keep playing.
A base version of Build will be free, with paid options for power users. The rollout will expand to more regions after the New Zealand alpha, and Roblox said it plans to share further creation tool announcements in the coming months. The platform has 132 million daily active users, any one of whom could now prototype a game from their phone.
Roblox is putting AI game creation inside its mobile app, giving more people a faster way to turn a written idea into a playable experience without starting in Roblox Studio.
The company will begin a public alpha of Build in New Zealand on July 28, 2026. The mobile-first AI tool turns text prompts into playable games inside the Roblox app and will include publishing among its selected early features.
Build adds a creation tab to the mobile app. A user can describe a game in ordinary language, and Build will generate an initial project with gameplay mechanics, environments, characters, visual styling, sound, and other elements.
Creators can playtest the result, request changes through chat, share the project with friends, or continue working in Roblox Studio. Build and Studio share the same back end, models, and chat history, so a project started on a phone can move into the company’s more advanced desktop tools.
Roblox is positioning Build as an easier entry point for people who have a game idea but don’t already use Studio. The creation platform reports 132 million daily active users and wants more of those players to become creators.
The initial rollout will remain limited. During the New Zealand alpha, Build is scheduled to be available to age-checked users 9 and older, although age requirements may vary by region.
Roblox is positioning Build as an easier entry point for people who have a game idea but don’t already use Studio. Image credit: RobloxBuild-created games that pass Roblox’s safety checks will be available worldwide to age-checked users 16 and older. Games must also complete Roblox’s extended review process before entering its Kids or Select catalogs.
Roblox plans to expand Build to more creators and regions after the New Zealand alpha, but it hasn’t announced a broader rollout schedule.
Build combines open-source models with Roblox’s proprietary AI systems. Roblox says its models use gaming-specific data and a large collection of 3D models to generate functional objects and scenes.
Roblox is also developing AI tools for professional creators. Planned agents will identify bugs, answer plain-language questions about analytics, and suggest experiments tied to engagement, retention, and monetization.
Some of the underlying technology is already available. Procedural Models generate adjustable 3D assets from text or images, while Roblox’s Cube foundation model can create functional objects, including vehicles that drive and weapons that shoot.
Roblox also plans a scene-generation model that will create editable, playable environments from a single prompt. The company hasn’t announced a release date.
Faster game generation could increase the number of repetitive or unfinished projects competing for attention. Roblox addressed that concern directly in its announcement.
The company said its discovery system prioritizes long-term retention, which Roblox argues excludes what it called “AI slop,” and Build-created games will compete in the same candidate pool as other experiences.
A basic version of Build will be free, with paid options planned for creators who need additional capabilities. Image credit: RobloxRoblox argues that games that fail to attract players will remain difficult to discover under its retention-based ranking system. Faster generation could still leave Roblox with more projects to review, rank, and moderate as Build reaches additional markets.
A basic version of Build will be free, with paid options planned for creators who need additional capabilities. Roblox hasn’t disclosed pricing or identified which features will require payment.
Build can shorten the path to a first playable project, but generating a game isn’t the same as making one people want to keep playing. Roblox’s discovery system will help decide which Build projects find an audience and which disappear into the platform’s growing catalog.
Amazon’s $400 discount on Apple’s high-end 16-inch MacBook Pro with an M5 Max chip and 2TB SSD is available now, with delivery as early as tomorrow for Prime members.
The M5 Max 16-inch MacBook Pro is on sale for $3,999 at Amazon in your choice of Space Black or Silver. This high-end configuration has Apple’s M5 Max chip with an 18-core CPU and 32-core GPU, along with 36GB of unified memory and a spacious 2TB SSD.
Save $400 on M5 Max 16″ MacBook Pro
Amazon’s $400 discount delivers the lowest price available per our 16-inch MacBook Pro Price Guide, with the next lowest price coming in at $4,189 at Expercom.
In our hands-on 16-inch MacBook Pro review, we found the M5 Max chip is blazing fast and we were happy to see the laptop now supports Wi-Fi 7.
You can also find MacBook Pro deals on M5 Pro 14-inch and 16-inch models in our Price Guides, with a few highlights below.

The past two years have transformed the world of software development, but there’s at least one area that remains largely untouched by artificial intelligence: the operating-system layer inside phones, vehicles, and other connected devices.
A Seattle startup called logcat.ai has raised $2.55 million to change that.
Co-founded by CEO Varun Chitre and CTO Tarun Vashisth, two engineers with years of experience building device software, logcat.ai is developing a system of AI agents that autonomously hunt down bugs across the kernel, modem, and firmware of devices running Android or Linux.
The pre-seed round was led by Founders’ Co-op, with participation from Act One Ventures, TheFounderVC, Shorewind Capital, Clayoquot Capital, and Alumni Ventures.
“It’s one of the toughest areas of software engineering, and it doesn’t get a lot of exposure. Operating-system engineering is virtually hidden today,” Chitre said in an interview.
It’s also a challenge for many companies given a shortage of engineers who specialize in the field, compared to the much larger population of developers who build apps and software that run on top of the operating system.
How it works: An engineer using logcat.ai uploads the log files a device generates when something goes wrong — such as bug reports and kernel logs — and logcat.ai’s software analyzes them together to find the root cause and point to where in the code to fix it. Each finding cites the exact log line it came from, so an engineer can check the work.
Currently, logcat.ai finds the root cause and recommends a fix. The larger plan is to have the AI write the fixes, test them, and eventually build new features on its own, with engineers approving the work before it’s deployed.
@media (max-width: 600px) {
aside.callout { float:none !important; max-width:100% !important; margin-left:0 !important; margin-right:0 !important; }
}
The long-term goal, Chitre said, is to become the standard tool for building and maintaining operating systems on new and existing hardware — from smartphones to cars to robots and other embedded systems — so a company can ship without a full-stack specialist on staff.
“We’re moving toward a world where software and intelligence extend far beyond our laptops and phones, yet the tooling to build high-quality products for that world is still missing,” said Aviel Ginzburg, general partner at Founders’ Co-op, in a statement.
He called Chitre and Vashisth “one of the only teams in the world truly up for the challenge.”
Traction: The company says it has served hundreds of engineering teams in a public beta, analyzed more than 10 billion lines of trace data, and run thousands of automated investigations. It’s generating revenue but isn’t ready to disclose numbers or customers.
Competitive landscape: Chitre said logcat.ai’s main competition isn’t another product but in-house scripts and the knowledge locked in a few senior engineers’ heads. App-level crash tools like Google’s Crashlytics and Sentry stop at the app layer and don’t do the deeper system debugging.
Specialist vendors and the contract manufacturers that build devices are potential partners more than rivals, Chitre said, since they face the same engineer shortage.
GeekWire first reported on logcat.ai in March, in a Startup Radar roundup.
The team: Chitre and Vashisth met at Esper, the Bellevue, Wash.-based device-management company, where they worked together for more than seven years. They started logcat.ai because they had spent years doing debugging by hand and knew what was missing.
Chitre has spent more than 13 years in the field, getting operating systems to boot and run on new hardware and porting new Android releases and Linux kernels onto older devices. He was also a maintainer of LineageOS, a widely used open-source version of Android.
Vashisth has led engineering teams working across Android, Linux, and iOS, and brings a background in large-scale distributed systems. At Esper, he rose to senior software engineering manager. His prior experience includes platform-architecture engineering at Target.
For now, the company is just the two founders: Chitre in the Seattle area, Vashisth in Bengaluru, India. They plan to hire about 10 people over the next year, with a distributed team working remotely from wherever they can find the specialized talent.
They know those hires won’t be easy to find, given the scarcity of people in the field. “That’s the same shortage our product exists to address,” Chitre said, “and we’re not exempt from it.”
Don’t expect that number to shrink any time soon.
Netflix hasn’t made any secret of its interest in artificial intelligence, and now we have a sense of how those tools are being used in its content. “In 2026, GenAI workflows have been used in roughly 300 of our titles, with the largest concentration of work in post-production,” according to the shareholder letter detailing its second-quarter financials. The company named three projects — Glory (India), Brasil 70: A Saga do Tri (Brazil) and The American Experiment (US) — that used generative AI “to create highly complex sequences,” but the tech is becoming more widespread at this point.
We already knew that Netflix had applied generative AI in at least one original show as of last July, but between making acquisitions and launching new specialized studios, its ambitions clearly extended further. The streamer went on to note in its earnings letter that “We are increasingly leveraging these tools to deliver higher quality output more quickly and at a lower cost than traditional methods.”
Here’s the recurring reminder that yes, gen-AI is capable of making something much quicker than a VFX artist or animator. But it still takes some human touch to make sure the results actually work with the rest of the film or show. And just because AI can be a useful tool for skilled creators doesn’t mean it should be tasked with replacing entire teams. Hopefully that’s something Netflix and its partner studios understand as they continue to double down on the tech.
Across 107 enterprises, AI agents are being given real access to systems and data while the controls meant to contain them lag behind. More than half have already had a confirmed agent security incident or a near-miss; only about a third give every agent its own scoped identity, and most agents still share credentials; and only three in ten isolate their highest-risk agents. The security stack is overwhelmingly borrowed from the model providers and hyperscalers rather than purpose-built for agents, spending remains a thin slice of the security budget, and enterprises are evenly split on whether their defenses are keeping pace with AI-enabled attackers. The result is an agent security gap — autonomous agents proliferating faster than the identity, isolation, and enforcement controls needed to hold them.
This wave of VentureBeat Pulse Research examines how enterprises secure their AI agents: what tooling they run, how they manage agent identity and isolation, what has already gone wrong, how much they spend, and whether they believe their defenses are keeping pace with AI-enabled attackers.
The central finding is an agent security gap — the distance between the autonomy enterprises are granting their agents and the controls in place to contain them. More than half of organizations (54%) have already experienced a confirmed agent security incident (18%) or a near-miss caught before harm (36%). The structural weakness beneath those numbers is identity: only about a third (32%) give every agent its own scoped, managed identity, while the rest report that some agents share credentials or that agents mostly run on shared API keys and human or service-account credentials. When agents share credentials, a single compromised or over-permissioned agent carries a wide blast radius — and only three in ten enterprises (30%) isolate their highest-risk agents in sandboxes to bound that radius.
What makes the gap notable is how comfortable enterprises are inside it. The security stack is overwhelmingly provider-native — OpenAI’s guardrails (51%), Google’s and Microsoft’s cloud controls, and Anthropic’s managed-agent controls dominate, while the dedicated agent-security specialists barely register — and satisfaction with that borrowed stack is high, averaging 4.2 out of 5. Yet spending remains a thin slice of the security budget, only a third of enterprises believe their AI defenses are ahead of AI-enabled attackers, and a clear majority plan to change tooling within the year. Enterprises are satisfied with controls they are simultaneously preparing to replace.
VentureBeat fielded this survey as part of its ongoing Pulse Research series, this instrument focused on enterprise agent security — the tooling, identity, isolation, and enforcement controls organizations use to secure autonomous AI agents. Responses are filtered to organizations with more than 100 employees (n=107; the survey’s smallest size band, 1–100 employees, is excluded), drawn from a single June 2026 wave. Because this is one wave rather than a pooled multi-month sample, the report reads cross-sectionally and does not infer month-over-month trends. Several questions were multiple-select, so those shares can sum to more than 100%.
By role the sample is senior and buyer-credible: 45% are final decision-makers for AI purchases and another 30% recommenders or influencers. Managers (43%), individual contributors (24%), VPs and directors (15%), and the C-suite (11%) make up the seniority mix. By organization size the sample is mid-market-weighted: 251–1,000 (42%) and 101–250 (25%) employees lead, with 1,001–5,000 (19%), 5,001–10,000 (8%), and 10,001+ (7%) above them. Technology/Software is the largest industry at 23%, followed by Manufacturing (15%), Retail/E-commerce (14%), and Healthcare/Life Sciences (13%).
At 107 respondents the sample is large enough to read directionally but should be treated as a directional signal rather than a precise measurement; it is self-selected and is not a probability sample. It skews toward the mid-market, so it is best read as the view from organizations actively standing up agent security rather than from the largest operators.
Satisfaction ratings are computed on the respondents who answered each rating question; the overall satisfaction score reflects 82 of the 107 qualified respondents.
More than half have had an agent security incident or near-miss
We asked whether organizations had experienced an agent security incident — a confirmed breach, or a near-miss caught before harm. Most that run agents in production had.
Finding 1 — The incidents are already here
42%
no such incident identified
36%
yes — a near-miss caught before harm
18%
yes — a confirmed incident
5%
not applicable — no agents in production; 2% don’t track this
This is the report’s defining number. More than half of organizations (54%) have already had an agent security event — 18% a confirmed incident and 36% a near-miss caught before it caused harm. Only 42% report nothing, and a small remainder either run no agents in production or don’t track such events. That so many report near-misses rather than only confirmed incidents is telling: enterprises are catching problems, but they are catching them close to the edge. The controls examined in the rest of this report — identity, isolation, enforcement — are what determine whether the next near-miss stays a near-miss.
Exposure scales with company size, but containment does not. The incident-or-near-miss rate rises from 49% in the mid-market (companies with 101-1,000 employees) to 63% at larger enterprises (above 1,000 employees), while sandbox isolation of high-risk agents falls from 35% to 20%, and satisfaction with security tooling drops from 4.36 to 3.97. The organizations running the most agents across the most systems carry the most incidents and the least of the one control that bounds an incident’s blast radius.
Only a third give every agent its own scoped identity
We asked how enterprises manage the identity of their AI agents — whether each agent has its own credentials, or agents share them. Full per-agent identity is the exception.
Finding 2 — The identity gap
48%
some agents have scoped identities, but many still share credentials
32%
each agent has its own scoped, managed identity
32%
agents mostly run on shared API keys or human / service-account credentials
7%
not applicable — no agents in production; 5% don’t know
Rolled together, the overlapping answers show 69% of enterprises (74 of 107) with credential sharing somewhere in the agent fleet. Identity is the structural weakness beneath the incidents. Only about a third of enterprises (32%) give every agent its own scoped, managed identity — the precondition for least-privilege access and clean attribution. Nearly half (48%) say some agents have scoped identities but many still share credentials, and another 32% say agents mostly run on shared API keys or borrowed human and service-account credentials. (Respondents could describe more than one pattern across their agent fleet, so these overlap.)
The consequence is direct: when agents share credentials, an over-permissioned or compromised agent can act with far more reach than intended, and forensics after an incident cannot cleanly tell which agent did what. The non-human identity problem — giving every agent its own governed identity — is the single largest unfinished piece of enterprise agent security.
Moreover, a company’s agent credential posture is correlated with incidents. Organizations with credential sharing anywhere in the fleet were hit — with an incident or a near-miss in the past twelve months — at 63.5% (47 of 74). Organizations where every agent carries its own scoped identity were hit at 40.9% (9 of 22). The fully-scoped group is small, so for now the relationship is an association rather than proven causation, and the gap is concentrated in the mid-market — but within a single survey, a twenty-three point difference in incident rate suggests significance.
Only three in 10 sandbox their highest-risk agents
We asked what an organization’s agent security posture looks like in practice — whether they observe, enforce, isolate, or some combination. The control that bounds damage is the least common.
Finding 3 — Observe and enforce, but rarely isolate
49%
enforce — agents have scoped identities and permissions, enforced at runtime
47%
observe — they monitor and log agent activity, but runtime enforcement is limited
30%
isolate — high-risk agents run sandboxed, with bounded blast radius if controls fail
6%
don’t know; 5% have no dedicated agent security program yet
Monitoring and enforcement are reasonably common; containment is not. Roughly half of enterprises observe agent activity (47%) or enforce scoped permissions at runtime (49%), but only 30% isolate their highest-risk agents in sandboxes that bound the blast radius when the other controls fail. That ordering is backwards from a defense-in-depth standpoint: observation tells you what happened, enforcement tries to prevent it, but isolation is what limits the damage when prevention fails — and it is the control enterprises have adopted least. Combined with the identity gap in Finding 2, the picture is of agents that are watched and permissioned but rarely boxed in, which is precisely the configuration in which a single failure propagates.
Guardrails from OpenAI, Google and Microsoft dominate; specialists barely register
We asked which agent security tooling enterprises use, and which is their primary layer. The answer favors the model providers and hyperscalers over the dedicated security vendors.
Finding 4 — Security runs on borrowed, provider-native controls
51%
use OpenAI’s built-in guardrails; 36% Google Cloud controls; 35% Microsoft Azure (Purview / Copilot Studio DLP); 29% Anthropic’s managed-agent controls
13%
Microsoft Entra Agent ID; 10% AWS Bedrock Guardrails
8%
each uses open-source guardrails, Cloudflare, and Cisco; the dedicated specialists (Palo Alto, CrowdStrike, Zenity, HiddenLayer, Lakera, Okta) sit in low single digits
82%
name a provider-native or hyperscaler control as their primary agent security layer
Enterprises are securing agents with tools that came bundled with their models and clouds. OpenAI’s guardrails lead at 51%, followed by Google’s and Microsoft’s cloud-native controls and Anthropic’s managed-agent controls — and when asked to name their single primary security layer, 82% name one of these provider-native offerings. The purpose-built agent-security category — Palo Alto’s Prisma AIRS, CrowdStrike, Cisco AI Defense, Zenity, HiddenLayer, Check Point’s Lakera, Okta for AI Agents, non-human identity platforms — barely registers, each in the low single digits, and only 5% run no dedicated tooling at all. As with retrieval and evaluation elsewhere in this series, the provider bundle is winning the default: enterprises reach first for the guardrails their platform ships, and the independent security layer that would address the identity and isolation gaps has not yet been adopted at scale.
The provider-default pattern is consistent across both Q2 survey waves. In April–May (n=110), usage was led by the same names — OpenAI’s controls at 26%, Azure at 15%, AWS at 14%, Google at 12% — with every dedicated agent-security specialist at 3% or below and one in ten using no dedicated tooling at all. The common finding from the two surveys: Enterprises are defaulting to the solutions provided by the platform they’re using, and the specialist category vendors have yet to become big players here.
(A note on reading these shares. As described in the methodology section, the respondent sample is self-selected and skews mid-market, and the usage question counted every vendor or approach a respondent has in place — so the figures measure presence in the security stack rather than spending or exclusivity. Individual vendor percentages therefore carry all the usual sample caveats. The structural pattern, however, held across both Q2 waves on two differently worded questions: provider-native and hyperscaler controls lead, and dedicated agent-security specialists remain in low single digits. Read the individual shares loosely and the pattern with confidence.)
Satisfaction is high, even as incidents mount and identity lags
We asked how satisfied enterprises are with their current agent security tooling. The comfort is notably out of step with the exposure documented above.
Finding 5 — And enterprises are comfortable with it
4.2
average overall satisfaction with current agent security tooling, on a five-point scale
4.1
average value for money; ease of implementation trails slightly at 3.9
54%
have nonetheless already had a confirmed incident or near-miss (Finding 1)
32%
give every agent its own scoped identity (Finding 2)
Satisfaction with agent security tooling is high — 4.2 out of 5 overall, and 4.1 for value for money — among the most positive readings in this series. That is the striking part: enterprises are highly satisfied with a stack that is mostly borrowed provider guardrails, even though more than half have already had an incident or near-miss and only a third give their agents scoped identities. The comfort appears to rest on the convenience and low friction of provider-native controls rather than on demonstrated containment. It is a false comfort in the making — the same enterprises expressing satisfaction are, as Finding 8 shows, a clear majority planning to change tooling within the year, which suggests the confidence is thinner than the score implies.
Most spend under a tenth of the security budget on agents
We asked what share of the security budget enterprises allocate to securing AI agents. For a fast-emerging risk, the allocation is modest.
Finding 6 — Budgets haven’t caught up
46%
allocate 6–10% of their security budget to agent / AI security — the most common band
26%
allocate 1–5%; a further 8% under 1%
9%
allocate more than 25%
Spending on agent security is still a thin slice. The most common allocation is 6–10% of the security budget (46%), and a third of enterprises (34%) spend 5% or less; only a quarter (24%) devote more than a tenth. Given the incident rate in Finding 1 and the identity and isolation gaps in Findings 2 and 3, the budget looks like a lagging indicator — the risk has arrived faster than the funding to address it. The enterprises spending more than a tenth of their security budget on agents are a distinct minority, and they are likely the ones building the scoped-identity and isolation controls the rest have not.
Only a third think their AI defenses are ahead of AI-enabled attackers
We asked how enterprises assess the balance between their AI-enabled defenses and AI-enabled attackers. Confidence is far from settled.
Finding 7 — The arms race is even, at best
35%
our AI-enabled defenses are ahead
21%
attackers using AI are ahead of our defenses
21%
too early to tell; 6% don’t know
Enterprises are split on whether they are winning. Only about a third (35%) believe their AI-enabled defenses are ahead of AI-enabled attackers; the rest are less sure — 32% call it roughly even, 21% think attackers are ahead, and another 21% say it is too early to tell. Taken together, a clear majority (53%) rate the balance as even or tilted toward the attacker. That uncertainty sits uneasily beside the high satisfaction of Finding 5: enterprises are content with their tooling yet unconvinced it is winning the contest it exists to win. In a domain where the offense is also compounding with AI, an even race is not a comfortable place to be.
Nearly six in 10 plan to adopt or switch tooling within a year
We asked whether enterprises plan to adopt a new, additional, or replacement agent security solution, and which they are considering. Few intend to stand pat.
Finding 8 — A security reshuffle is coming
41%
have no plans to change
29%
plan to adopt or switch within the next 0–3 months
The security stack is not settled. While 41% have no plans to change, a clear majority (59%) intend to adopt a new, additional, or replacement agent security solution within twelve months, and 29% within the next quarter — a strong signal that, high satisfaction notwithstanding, enterprises know the current stack is provisional. Incidents are what start the buying cycle.
Among organizations that have been hit, 42.1% plan to adopt, add, or replace agent security tooling within the next ninety days, against 14.0% of organizations with no incident — and after a confirmed incident it becomes majority behavior, at 52.6%. Getting hit also changes the threat assessment: 33.3% of hit organizations say AI-armed attackers are ahead of their defenses, against 8.0% of the unhit. Experience, in this data, is the strongest predictor of both urgency and pessimism.
The consideration set still leans provider-native (OpenAI 34%, Google 30%, Anthropic 29%, Azure 25%), but the dedicated security vendors — Cloudflare, Cisco, Palo Alto, Okta, Check Point’s Lakera — draw early interest in the mid-to-high single digits, more than their current footprint.
What the shopping does not yet include is the identity layer specifically. Twelve percent of the respondents include an agent-identity product — Okta for AI Agents, Microsoft Entra Agent ID, or a non-human identity platform — anywhere in their consideration set, and among the credential-sharing organizations that have already had an incident, identity consideration is essentially unchanged, at roughly one in ten. The control most directly implicated by the incident data is the one largely missing from the purchase plans. Whether this wave hardens the provider-native default or finally opens the door to purpose-built agent security — the identity and isolation controls the incidents call for — is the question this series will keep tracking.
Organizations with more than 100 employees are giving AI agents real reach into systems and data while securing them with controls built for something else. More than half have already had an incident or near-miss; only a third give every agent its own scoped identity, and most still share credentials; only three in ten isolate their highest-risk agents; and the stack doing this work is overwhelmingly borrowed from the model providers and hyperscalers rather than purpose-built for agents.
The uncomfortable pairing is confidence with exposure: satisfaction with the current tooling is among the highest in this series, yet spending is a thin slice of the security budget, only a third believe their defenses are ahead of AI-enabled attackers, and a clear majority are already planning to replace what they have. At 107 respondents in a single wave this is a directional read, skewed toward the mid-market — but the direction is clear: agent adoption is running ahead of agent security, and the controls that matter most when something fails — scoped identity and isolation — are the ones enterprises have built least. The agent security gap is not a coverage problem that a provider guardrail will close on its own; it is a problem of identity, isolation, and enforcement built for autonomous software. The open question for later waves is whether enterprises close it deliberately — or whether a confirmed incident closes it for them.
Based on survey responses from 107 qualified enterprise respondents (100+ employees), drawn from a single June 2026 wave. This is a directional read, not a precise measurement — the sample is self-selected and skews mid-market, so it’s best read as the view from organizations actively standing up agent security rather than from the largest operators. Respondents are senior and buyer-credible (45% final decision-makers, 30% recommenders/influencers), spanning managers through the C-suite, and drawn primarily from Technology/Software, Manufacturing, Retail/E-commerce, and Healthcare/Life Sciences.

A technological time capsule of artifacts from the Seattle region’s aerospace history was saved from the waste bin by an electronics recycler this week. Now he’s trying to solve the mystery: Who owned them, where did they come from, and what exactly are they, anyway?
Computer and electronic parts dating back nearly 50 years were among a donation of items dropped off at the Bellevue, Wash., location of Living Green Technology. Instead of the usual assortment of obsolete laptops, gaming consoles and tangled cords, the lot was like a pristine engineering archive consisting of gold-plated prototype chips, raw silicon architectures exposed under glass, and experimental fiber-optic cables used to pioneer early flight control systems.
Tyler Rivers, founder and CEO of the 13-year-old company, personally inspects weekly collections from his company’s public drop-off sites, and he instantly realized the pieces were far too rare to be shredded for their precious metals.
“I’m kind of the nerd for all this stuff,” Rivers told GeekWire on Wednesday. “I go down many, many rabbit holes with different things.”
Rivers was looking into whether the donor could be tracked down to help piece together the high-tech puzzle. He did his own digging and GeekWire also leaned on Google’s Gemini AI to help identify items in photographs Rivers shared. We’re hoping readers might also email us with their own insights.
For now, we’ve determined that the collection paints a picture of a highly specialized, Cold War-era engineering workspace focused on the physical dawn of modern aviation, spacecraft engineering, and early fiber-optic data networks. It includes:
Texas Instruments SBP9900X microprocessor: A rare, military-grade 16-bit processor from 1977 marked “Experimental.” Built using a specialized architecture resistant to extreme temperatures and ionizing cosmic radiation, this line of chips was famously utilized by NASA and military defense contractors for deep-space and missile guidance systems. (Check out this report on testing radiation-hardened microprocessors.)

Canstar 8×8 optical star coupler: A beautifully preserved, heavy-duty glass-and-metal fiber-optic coupler stamped “8X8 100/120/140.” This component physically fused fiber-optic strands together to split and route light signals — a critical building block for prototyping early, interference-proof “Fly-by-Light” flight control systems.

DDC Total-AceXtreme avionics module: A mechanical engineering sample marked by Data Device Corporation (DDC), a pioneer of 1970s and ’80s military flight systems. The component is designed for MIL-STD-1553, the standard data bus protocol that allows cockpit flight computers, sensors, and avionics to communicate with one another on military aircraft and spacecraft.

Un-lidded hybrid microcircuits: Custom-engineered ceramic and metal cavities housing bare silicon architectures connected by microscopic, gold-bonded wire arrays. These high-reliability hybrids were custom-crafted by hand for military and aerospace programs to pack dense electronic circuitry into compact, hermetically sealed packages.
Rivers has no formal aerospace, computer science or electronics background — he’s a 2012 University of Washington graduate in economics. He started his company as a college student while working at a UPS Store, setting up a drop-off bin on the counter to collect, repair, and resell old cell phones and iPods.
Today, in addition to public e-recycling, Living Green Technology assists businesses, government agencies and others in secure data destruction, asset recovery and more.
Rivers’ hands-on curiosity regularly follows him home. When unique or puzzling items show up at his public drop-off sites, he often takes them home to dissect them in his garage. Among his previous saves is a NASA laptop, complete with receipts and tagging showing it was modified for spaceflight.
“I pretty much deep dive and gather as much information as I can,” Rivers said. “Usually, sadly after that, I stick it on a shelf in my workshop and just leave it there until I figure out what I want to do next with it.”
This particular assortment of salvaged history offers a physical look at engineering hurdles solved decades ago, representing a transition period when computers were first being ruggedized to survive the extreme environments of military aviation and space flight.

For further insight, GeekWire reached out to Andrew “bunnie” Huang, a renowned hardware hacker, author, and MIT-trained electrical engineering Ph.D. widely known for his pioneering work in reverse engineering and open-source hardware. His blog is a hardware geek’s must-read.
After reviewing photos of the Bellevue haul, Huang pointed out that the collection may not actually be a single, unified archive from a lone aerospace project. Instead, he suspects it is the ultimate “collage” of high-tech souvenirs.
“The random tray of components on the black ESD foam… I almost would be inclined to think this was more of a collage of components kept by a technician from various projects,” Huang said. “There’s some pretty nice optical sensors in there with enormous active areas, a random segmented LED display, and an old 2K EEPROM.”
Given the Seattle region’s history around aviation, aerospace and technology, there are surely countless boxes stuck in garages, attics and storage spaces holding the artifacts of innovation.
Lāth Carlson is the former executive director of Living Computers: Museum + Labs, the now-closed Seattle institution founded by Microsoft co-founder Paul Allen as a home for vintage computing equipment. Carlson was accustomed to random boxes showing up on his doorstep.
“Many people don’t realize that most museums would not exist without collectors — people that say, ‘well, that seems like it’s worth keeping’ and put it in a box,” said Carlson, who now leads Seattle’s National Nordic Museum. “Sometimes we get really lucky and they end up being more right than they realize.”
Without speaking for local e-recycling outfits, Carlson recommended getting in touch before just leaving things at a museum, because most are bound by policy to dispose of such items.
For now, Rivers’ latest rescue is safe from the shredder, perhaps waiting for its full story to be uncovered.
The staff member allegedly made over $100,000 on Kalshi.
Gabriel Perez, President Donald Trump’s teleprompter operator, has been placed on administrative leave after it was discovered he bet on dozens of the President’s speeches on Kalshi, ABC News reports. Officials from the Commodity Futures Trading Commission, the body that currently oversees betting platforms like Kalshi, are reportedly willing to settle with Perez if he returns his winnings.
Perez allegedly made more than $100,000 betting on the length of President Trump’s speeches, including the State of the Union address, a speech at the World Economic Forum in January and remarks at a Medal of Honor ceremony in March. “Perez typically has the final eyes on nearly all of the president’s prepared remarks,” ABC News writes, which likely made it easier to place informed bets. If that wasn’t enough of a giveaway, Perez reportedly backed out of certain bets when Trump went off script.
Kalshi “promptly flagged and referred” those trades to the CFTC, according to a statement provided to ABC News, and Perez has reportedly already confessed to some of the trades in an interview with investigators. At a press conference, White House Press Secretary Karoline Leavitt said that the President is aware of the Perez’s actions and called them “deeply unfortunate” and a “disgrace.” Leavitt added that Perez had been put on unpaid administrative leave and that he will “no longer be here.”
In April 2026, Kalshi introduced new policies to prevent politicians and athletes from betting on their own elections or games. The company later suspended three political candidates from its platform for breaking those same policies. Kalshi introduced further restrictions in June, requiring users to disclose where they work before placing certain bets.
Attempts to tamp down insider trading might not have done much to discourage anyone, and states trying to regulate prediction markets have been blocked. After New Jersey banned Kalshi, a US Circuit Court of Appeals ruled the state had no right to ban the platform, putting power firmly in the CFTC’s hands.
SpaceX abruptly aborted the second attempted launch of its upgraded Starship rocket system on Thursday, just moments after the booster ignited at the company’s complex in South Texas.
CEO Elon Musk said on his social media platform X that “[s]ome of the engines didn’t start, triggering an automatic launch abort” and that the company will replace two of them. SpaceX won’t try to launch Starship again until next week, he wrote.
SpaceX was hoping to launch its first third-generation Starlink satellites into space — although they are supposed to burn up around 20 minutes after deployment, as Starship has not yet demonstrated the ability to reach Earth orbit.
This is also SpaceX’s first Starship test launch attempt since it went public on June 12 in the largest IPO in history. The company raised more than $85 billion in the transaction and briefly touched the valuations of Amazon and Microsoft, though its stock has steadily fallen over the intervening month.
On Thursday, SpaceX’s stock price closed below its IPO price of $135. Its stock sank more than 4% in after-hours trading after the aborted launch.
SpaceX was trying to return to flight just a few weeks after the first-ever launch of Starship V3 in May. That mission was a mixed bag.
Getting off the launchpad with the first version of a newly upgraded rocket was a big step forward, and the company was able to deploy a number of Starlink simulators into space. But the Super Heavy booster stage suffered a failure before it could attempt a simulated landing in the Gulf of Mexico, leading to an FAA-ordered review of what went wrong. (The FAA cleared the company to fly Starship again earlier this week after identifying a number of causes and fixes for the booster failure.)
Starship’s upper stage also lost an engine on its way to deploying the Starlink simulators during the May mission. The upper stage was able to perform its own simulated landing over the water without a hitch.
SpaceX was hoping to take another step forward Thursday by launching the V3 Starlink satellites. The upgraded Starship and Starlink are key to SpaceX’s incredibly ambitious plans to prove that the concept of “orbital data centers” is both technologically and economically viable. Starlink is also the largest revenue generator and the only profitable portion of SpaceX’s business.
Thursday’s launch attempt looked to be chugging along just fine, with only a brief hold in the countdown at T-minus one minute before the scheduled launch attempt. That hold cleared quickly, and the countdown resumed.
As the countdown expired, the launchpad’s water deluge system fired up, and the booster stage visibly began firing its engines — only for everything to suddenly shut down. Graphics on SpaceX’s broadcast appeared to show that four of the company’s new Raptor engines did not fire upon ignition.
SpaceX now has to take all the propellant out of both the Super Heavy booster and the upper stage, before determining exactly what went wrong on Thursday.
This story has been updated with new information from Elon Musk.
When you purchase through links in our articles, we may earn a small commission. This doesn’t affect our editorial independence.
![]()
GMC chose the spotlight of the 2026 ESPYS in New York to reveal a special edition built to mark 25 years of the Hummer nameplate. The 2027 Hummer EV Icon 25 arrives as a limited run available on both pickup and SUV body styles, and it carries a color choice that reaches back to the model that first turned the brand into a mainstream attention grabber.
A brilliant new color dubbed ICON covers the body in a modern spin on the bright yellow that became so common on Hummers beginning in 2002. That eye-catching red truly stands out against a black front grille, tightening up the look of the lower front end in a very stunning way. New 22-inch wheels join the broader 2027 lineup and complement the Hummers’ aggressive proportions nicely. Anyone who wants the Icon 25 treatment may get it on either the 2X or 3X trim level, resulting in the super-sized posture and road presence that Hummers have long been known for, whether driving through the city or leaping down a lonely trail.
Sale
![]()
Every one of these cars has its own unique serialized badge on the instrument panel, because even though they are part of a limited run, every owner wants to know that his Hummer is unique. The interior is completely black, with Jet Black materials on the seats, door panels, and trim, which contrasts nicely with the colorful outside. The drive mode area of the big screen also features distinctive visuals that reference design elements from prior Hummer models. To sweeten the deal, an exclusive keepsake item is included with each Icon 25, adding a true tactile touch to the anniversary and limited edition status of the car.
![]()
The performance story is similar to that of the rest of the Hummer EV line, in that it remains consistent but scales up depending on the configuration. The top-of-the-line 3X versions, equipped with the largest battery pack possible, deliver an estimated 1,160 horsepower and lots of torque to the wheels. They can go from 0 to 60 mph in 2.8 seconds flat, however only under regulated conditions. The 2X models still have enough power to perform pavement and off-road jobs with ease.
![]()
Out in the wild, these trucks’ off-road systems continue to set them apart. The adaptive air suspension can change the ride height on the fly, and with a single button press, it can raise the body by roughly six inches when you truly need the extra clearance. Four-wheel steering makes it easy to perform tight bends at low speeds, and the technology even allows you to drive sideways when you need to get into a tight place. The pickup’s 18 camera views come in handy when traveling at low speeds or when something is blocking your view.
![]()
All 2027 Hummer EV vehicles now come equipped with a North American Charging equipped connector, allowing you to plug directly into a Tesla Supercharger station without the need for a special converter. The capacity to operate as a power source and supply power to your home is also carried over, as long as you choose GM Energy gear and installation. Production of the Icon 25 edition begins later in 2026 at GM’s Factory ZERO in Detroit and Hamtramck, Michigan. Pricing and the total quantity of automobiles for sale will be announced closer to when deliveries begin. The Icon 25 goes on sale in the United States and Canada later this year.
[Source]
Weekend Open Thread: Nutriplenish Leave-In Conditioner
London Mayor Sadiq Khan handed a peerage by Keir Starmer alongside 15 other Labour figures… just days before the PM leaves No10
CFTC blocks Kalshi from unwinding Michigan trades after court order
Super Eagles star Moses Simon opens up on Liverpool transfer regret
Nvidia Stock Slips After Big Tuesday Rally as Huang Confirms Vera Rubin Chip Is Now in Production Today
Young campaigners urge incoming PM to act on outdoor junk food ads
XRP BOMBSHELL… XRP OMBOARDED FOR TRANSACTIONS!!!
Get Your ESP32 Sunny Side Up With This Solar Dev Board
Disney’s Most Ambitious Failed Star Wars Attraction Is Coming to SDCC
Dark Secrets Emerge When Jailbreaking LLMs
Injective Submits SEC Transfer-Agent Registration to Onchain Ownership Records
New Cornerback Enters Vikings Trade Rumor Mill
how to make coin bank box with cardboard #scienceproject #money #diy #shorts
Cloudflare Precursor Watches Your Mouse and Keyboard To Decide If You Are Human
Banco Bilbao Vizcaya Argentaria, S.A. (BBVA) Discusses Global Macro Environment and Economic Outlook for Core Markets Transcript
Ripple, Coinbase, Circle Join Linux x402 Foundation to Help Shape AI Payments
Nephros, Inc. (NEPH) Discusses Evolving Water Safety Strategies and Expansion Beyond Filtration Transcript
Vicki Gunvalson Defends Discussing Heather Dubrow’s Money
Claude Fable 5 Slips to Second in AI Coding Leaderboard
ACCC warns AI could lift insurance costs in risk-prone areas
You must be logged in to post a comment Login