AI on Ilscipio - Enterprise Commerce Experts

Local AI vs. Cloud APIs - When Each One Makes Sense

Fri, 28 Aug 2026 00:00:00 +0000

I run local models on my own hardware for some tasks and cloud APIs for others. People ask which one is better as if it is a philosophical question. It is not. It is a cost and latency question, and the answer depends on what you are doing.

When local makes sense

If you have a task that runs thousands of times a day with short inputs and predictable outputs - classification, extraction, simple Q&A - a local model is cheaper. You pay for the hardware once (or rent a dedicated GPU) and run as many requests as you want. No per-token billing, no rate limits, no dependency on someone else’s uptime.

I Forgot About My AI Inference Bill for a Month

Tue, 18 Aug 2026 00:00:00 +0000

I run a service that routes AI inference to the cheapest available GPU. So I spend an unreasonable amount of time staring at provider pricing dashboards. And the thing I keep learning is that the sticker price on an AI model tells you almost nothing about what inference actually costs you.

Take a 70B parameter model. Provider A charges $0.60 per million input tokens. Provider B charges $0.90. Provider A is cheaper, right?

How a Spreadsheet Turned Into an AI Inference Router

Fri, 14 Aug 2026 00:00:00 +0000

I accidentally stumbled on spot market pricing for AI compute. So naturally, I built a service around it.

The short version: GPU prices vary wildly between providers. Same model, same output, different costs depending on when and where you run it. An H100 on one provider costs $2.10/hr right now. Same GPU on another, $3.80/hr. Tomorrow those numbers will be different again.

I found out the hard way. I was running AIVory Guard on a single provider, picked because it was cheapest when I checked. A month later the bill was 40% higher than I expected. The prices had moved and I had not noticed.

I Replaced Five API Wrappers With MCP in a Weekend

Tue, 11 Aug 2026 00:00:00 +0000

I spent the first half of 2025 writing custom API wrappers so that AI models could talk to our internal tools. A wrapper for the marketing API, one for the sales dashboard, one for the JetBrains Marketplace stats, two more for deployment scripts. Every wrapper was slightly different. Every one broke when the tool’s API changed. And every time I wanted to connect a new AI client, I had to write the integration again.

A SQL Injection Got Through Two Code Reviews

Fri, 07 Aug 2026 00:00:00 +0000

Last month a junior developer on a client project pushed a SQL query that concatenated user input straight into the WHERE clause. Classic injection. The pull request had two approvals from senior engineers. Nobody caught it.

This is not unusual. Code review catches logic bugs, style violations, missing tests. It is not great at catching security patterns. Reviewers scan for intent and correctness - does this code do what it is supposed to do. They are not running OWASP categories through their head while reading a diff.