Back to blog

Local AI: Your Data and Your Costs Under Control

11/5/2026
Post by

Every time someone on your team asks an AI tool to summarize a contract, clean up a customer database or retouch the photos for a launch, that information travels to a server you don’t control. Local AI takes the opposite route: the model runs on your own hardware and the data never leaves the company, so it stays private. For sensitive, continuous or offline workloads, it is already the most convenient option. For everything else, the cloud still wins.

The problem is that this decision is rarely made consciously. Almost half of companies admit their employees have already entered non-public information into generative AI tools (Cisco, via Constellation Research, 2024). And on the other side of the counter, customers notice: in the United States, 71% of adults believe the growing use of AI will make their personal information less secure, and only 3% think the opposite (Pew Research Center, 2026).

With AI already part of everyday work, the question worth asking is which part of that work should run where your data already lives.

My cameras don’t report to anyone

When I built the security system for my home, I set it up with seven 4K cameras processed right there with Frigate, an open-source video recording software. Car, person and face detection runs on a local accelerator. I’m now replicating that same system in my new house.

The alerts are custom. If a car enters the driveway area at night, the garage light turns on for five minutes; the rule is limited to that zone to avoid false positives. No private video leaves the house, there’s no subscription and no third-party server.

The clearest contrast is Ring, Amazon’s home camera brand, which processes video in the cloud. Two recent events show what that means:

  • Availability. On October 20, 2025, AWS suffered an outage in its US-EAST-1 region that lasted more than 15 hours (ThousandEyes, 2025). Ring was among the affected services, along with Snapchat and Venmo (Tom’s Guide, 2025). A local system kept recording and sending alerts.
  • Privacy. In September 2025, Ring launched Search Party, an AI feature that connects a neighborhood’s cameras to look for lost pets and comes enabled by default (Biometric Update, 2026). The 2026 Super Bowl ad promoting it sparked a massive backlash over surveillance fears, and that same week the brand canceled its integration with Flock Safety, a camera network used by law enforcement (Fortune / AP, 2026). Two months earlier, it had launched Familiar Faces, a facial recognition feature for cataloging people who visit the home (TechCrunch, 2026).

My system does exactly the same thing as Ring. The difference lies in where the video stays and who decides what happens to it.

It fails too, of course. Once, the disk filled up and detection events stopped closing. With local, the problem is yours, but so is the fix: you don’t wait 15 hours for a provider to solve it.

‍

If it’s so good, why weren’t we doing it before?

Because until two years ago, running your own model was a technical curiosity with mediocre results. That changed fast:

  • Since January 2026, the best open-weight models have been, on average, about four months behind the most advanced closed models (Epoch AI, 2026).
  • With a single high-end gaming GPU, a graphics card with 8 or 12 GB, you can already run models locally that match the frontier of 6 to 12 months ago (Epoch AI, 2025).

There’s an important nuance: the open model that truly catches up with the frontier usually has hundreds of billions of parameters and needs a server, not a laptop (Modelfit, 2026).

For business, that’s more than enough. Removing backgrounds, classifying, summarizing, detecting objects or generating variants doesn’t require the most powerful model in the world. A very good one running on your own equipment does the job.

‍‍

What your company gains with local AI

Three benefits support the decision to bring an AI workload in-house: data control, operational continuity and predictable cost.

1. Your data stops traveling to places you don’t know

Leaks often start with a well-meaning employee who pastes confidential information into a public tool because it solves the problem faster. According to IBM and the Ponemon Institute’s annual Cost of a Data Breach report, a high level of shadow AI (employees using unapproved AI tools) added USD 670,000 to the average cost of a breach, and 63% of the 600 organizations surveyed had no policies to govern AI use (IBM, 2025).

Banning it rarely works. What does reduce the incentive is giving the team an internal AI that is just as useful, running on your own infrastructure, where the contract, the customer database or the code never leave the company.

Protecting customer data is also a commercial advantage. Among the companies surveyed by Cisco, 94% say their customers wouldn’t buy from them if they didn’t protect their data properly (Cisco, via Govtech Review, 2024), and 95% say the benefits of investing in privacy outweigh the costs, with an average return of 1.6 times the investment (Cisco, via Outlook Startup, 2024). For a brand, being able to explain with certainty where its customers’ information is processed translates into trust, less friction with its own clients’ legal and procurement teams, and a concrete argument against the competition.

2. Your operation keeps running even if the provider goes down

The October 2025 AWS outage had the greatest impact of the 38 that IncidentHub, an independent incident aggregator, recorded that year, and it affected hundreds of SaaS providers at once (IncidentHub, 2025).

Outages are the most visible dependency, but there are others: usage limits, rising prices, models the provider changes or discontinues overnight. In our previous article, we saw how a measurement provider could change its methodology and force an entire industry to recalibrate. The same thing happens with AI models. A local model keeps working the same way for as long as you decide.

3. Your cost stops growing with every use

A Cloudian survey of 203 IT decision-makers found that 93% of companies have already moved AI workloads off the public cloud, are doing so or are evaluating it, and almost half point to unpredictable cloud costs as a barrier (Cloudian, via StorageNewsletter, 2026). The figure should be read with care: Cloudian sells on-premises infrastructure.

The rule of thumb is simple. If the workload runs all day, every day, your own hardware pays for itself. If it’s sporadic, the cloud still wins.

Speed shows up as an extra benefit in some cases: a camera alert, a kiosk or an event experience needs an immediate response, and without connectivity the cloud simply doesn’t exist. It shouldn’t be sold as a universal advantage, though: a small local model responds fast, and a large cloud model still reasons better.

‍Where local AI makes sense: five use cases

A workload is a good candidate when it meets at least one of these conditions: it handles sensitive data, it runs continuously or it has to work offline. These are the cases where the difference shows the most.

1. High-volume image processing. Removing backgrounds, cropping or generating variants of thousands of product photos is repetitive and predictable, the ideal scenario for paying off hardware. Plus, launch images don’t circulate through someone else’s servers ahead of time.

2. Experiences with audience photos. In photo booths and brand activations, a person’s face is their most personal data. Processing it on site avoids sending it to third parties and lets the experience work even when the event has a poor connection.

3. Video analytics. Foot traffic counting in a store, heat maps or security event detection. It’s the same principle as the home cameras, applied to retail: video is analyzed where it’s recorded, 24/7, without using bandwidth to upload it.

4. Internal assistant for confidential documents. Legal, HR or finance can query contracts, personnel files or reports with AI without those documents leaving the company. It’s also the most concrete way to reduce shadow AI.

5. Regulated data. In healthcare, banking or the public sector, keeping processing within your own infrastructure simplifies regulatory compliance and auditing, especially with specially protected data such as biometrics.

There’s more: call transcription in sales and call centers, catalog enrichment in e-commerce, coding assistants on proprietary repositories, or field operations with poor connectivity, such as in agriculture, logistics or energy.

‍

What we’re already doing

We work closely on the first two cases on the list, and each one shows a different benefit.

Thousands of backgrounds a day, without paying per image

In an API project for a client, we process thousands of images a day to remove their backgrounds. It’s a trivial task, but at that scale it comes with complications: cost per image, dependency on an external service, queues and usage limits.

We replaced the cloud service with a local one, running on our own hardware. With that change, the client stopped paying more than USD 1,000 a month to the service it used before.

The lesson applies to any company: a repetitive, predictable, high-volume task is the ideal candidate to bring in-house. Removing a background doesn’t require the most powerful model in the world.

Photo Booth: AI portraits that never leave the event

We’re developing a Photo Booth service that creates AI portraits of people, running 100% locally, designed for events and brand installations.

The main differentiator is privacy: the audience’s image is processed on site, stored for a limited time, not linked to any other user data and not shared with third parties. The secondary one is availability: since it works offline, the experience doesn’t depend on the venue’s network.

A person’s face is biometric data, and across much of the Americas it has reinforced protection. In Brazil, the LGPD considers it sensitive data whenever it is linked to a person (Barbieri Advogados). In Mexico, the personal data law in force since March 2025 requires informed consent and provides for fines of up to 69 million pesos for misuse of sensitive data (Portal ERP, 2025). In Argentina, the data protection authority treats it as sensitive when it can reveal potentially discriminatory information (AAIP, Resolution 4/2019). And in Illinois, BIPA requires written consent before capturing face geometry, with fines of USD 1,000 to 5,000 per violation (Bloomberg Law). Processing the image on site reduces the risk, but it doesn’t replace asking for that consent.

In an activation, sending a photo of someone’s face to an external server to apply AI is a risk many brands take on without knowing it. Processing it on site eliminates that risk. At event scale, it’s the same principle as the home cameras: faces and privacy, from the living room to the activation.

‍

What going local costs (and why it pays to know beforehand)

Building in-house has real costs, and it’s worth putting them on the table:

  1. Upfront investment and maintenance. Hardware, power, updates and someone to run it. The full disk on my cameras is a good reminder.
  1. Capability ceiling. For complex reasoning, the most advanced cloud models are still ahead.
  1. Sporadic workloads. If your team uses AI two hours a week, your own hardware won’t pay for itself.
  1. Security becomes your responsibility. A poorly configured local server is riskier than a serious cloud provider.

That’s why the model that works best is hybrid: local for what’s sensitive, continuous or needs to work offline; cloud for what’s sporadic or needs the most powerful model available.

‍

Three questions to ask yourself this week

  1. What data from my company, or from my clients, is going out to third-party AI tools today?
  1. What process stops if my AI provider goes down for 15 hours?
  1. Which AI workload runs all day, and am I paying for it per use?

‍In our previous article, we argued that the data generated by your own investment is yours, and that this right is negotiated before signing, not after. If you haven’t read it yet, you can find it here.

This article is the other half of that discussion. Regaining control of your data does little good if you then process it with an AI that takes it out of the house, sets its own rules and charges you every time you use it. First, make sure the data is yours; then, make sure the AI that works with it is yours too.

In the end, the most useful AI isn’t always the biggest one. Sometimes it’s the one that runs where your data already is.

At Portinos, we help companies bring AI into their own infrastructure, with solutions designed for their business and their data.

Let's talk!

Tell us about the project

*Requied fields

By agreeing, you acknowledge that Portinos may collect, use, and protect your personal information as described in our Privacy policy.

Thank you, message received!
We’ll be in touch soon — hang tight!
Oops! Something went wrong while submitting the form.