Our Work
What we build, the part of it that is actually hard, and the stack it runs on
How to Read This Page
Agave Information Solutions has been building software in Scottsdale since 2008. Client names and screenshots are not published here, so instead of a gallery you get the straight version: the kinds of systems we build, the technical problem each one actually turns on, and the tools we build it with.
If you want to judge us before you call, judge the description of the hard parts. Anyone can list technologies. Knowing which failure mode bites at which scale is the part that comes from having shipped it.
Custom Development
Line-of-business applications, internal tools, APIs, and the integrations that connect them to the systems a company already runs.
The hard part: Replacing a spreadsheet or an aging in-house app without stopping the business that depends on it. That means reading the existing data, writing down the rules nobody ever wrote down, and cutting over in stages instead of one weekend.
Stack: .NET, C#, TypeScript, React, Next.js, PHP, Python, SQL Server, PostgreSQL
Database Architecture
Schema design, indexing strategy, partitioning, and query optimization for applications where the data is the product.
The hard part: Queries that are fine at a gigabyte and fall over at a terabyte. Execution plans flip from seek to scan, statistics drift, implicit type conversions quietly disable an index, and a report that ran in a second starts timing out.
Stack: SQL Server, PostgreSQL, MySQL and MariaDB, Redis, pgvector
NAS Infrastructure and Custom Apps
Business storage deployments, plus the software that indexes, moves, and serves whatever ends up on them.
The hard part: Storage is easy to buy and hard to organize. Tiering policy, catalog design, and verified ingest are what turn a stack of disks into something you can find one file in without mounting everything.
Stack: QNAP, Synology, TrueNAS, Unraid, LTO tape with LTFS
.NET Modernization
Migrations off legacy .NET Framework onto current .NET, with a cloud-ready shape at the end of it.
The hard part: Web Forms postback logic, WCF contracts, and VB.NET business rules that exist only in the code. We map the behavior first and move it second, so the new system does what the old one did before anyone is asked to trust it.
Stack: Web Forms to Blazor, ASP.NET MVC to ASP.NET Core, Entity Framework to EF Core
Hands-On Infrastructure
Network configuration, server and rack installation, and on-site troubleshooting. Drills, drives, wires: the full stack.
The hard part: A surprising share of software problems are power, cabling, or a switch config. Being able to stand in front of the rack ends that argument in an afternoon instead of a week of email.
Stack: On-site across the Phoenix metro, remote everywhere else
IT Specialist Retainers
Ongoing hardware and software support on a standing retainer, including monitoring, patching, backup verification, and vendor coordination.
The hard part: Nobody hands over the whole picture on day one. Retainers work because the same engineer keeps the context, so the next problem gets diagnosed against what we already know instead of from scratch.
Stack: Long-term engagements with mid-market companies and startups in Arizona
Where the Scale Language Comes From
Before Agave, Jason Jacoby founded Tempest Telecom in 1996 and built it into the first Internet roaming service to provide access on all 7 continents, running a unified AAA platform that combined voice, dialup, WiFi, and satellite connectivity.
Agave designed and operated the database systems behind a 2+ petabyte video platform at Tempest Telecom: metadata indexing, ingestion pipelines, delivery telemetry, and operational reporting. That is where the petabyte-scale and archive design language on this site comes from. It is not a figure of speech.
Read the longer version on the about page.
Want to Talk Through Your Project?
Free quote, no obligation. Scottsdale-based since 2008.