Aternex is Austin Lippert’s software practice, and he does the work himself. Every engagement follows the same four steps, starts with a call, and measures the system before changing it.
The same sequence whether Aternex joins your team or takes one problem end to end.
You describe the system and what is wrong with it, in your own words; there is nothing to prepare. If the work is a fit, the next step is access. If it is not, you will hear that plainly.
Aternex gets access to the code, the environments and the data it is allowed to see, runs the system end to end and measures it before anything changes: how long the slow parts take, where the time goes, which tests exist and which fail. That is the baseline every later claim is checked against.
The first change targets whatever dominates the problem. It goes in behind tests and through your own review process, so your team sees exactly what changed before it reaches production.
You get a written account of what was measured, what was fixed, what it changed, and what is worth doing next, in order. It stays useful whether or not the work continues.
Contract, full-time or one defined problem: all three are welcome. Pick the one that matches how you hire.
Austin joins your team as a contractor and works in the stack, repositories and process the team already runs.
Fits when: You have a team and a backlog, and you need a senior engineer who can take on the hard parts.
Austin joins your company as a full-time employee and owns modernization and delivery from inside the team, for the long run.
Fits when: You are hiring a senior engineer to stay, and the role is about modernizing legacy code and data or building something new.
Aternex takes one defined problem, from the first measurement to the fix running in production, and hands it back documented.
Fits when: Something specific is slow, fragile or missing, and nobody on staff has the time to own it.
I use AI agents every day, and how they touch your data is agreed per project. Claude and Codex work on code and tasks that involve no private data. When data has to stay private, I run agents through zero-data-retention endpoints, where the provider keeps nothing, or on models that run entirely on local hardware, where it never leaves the machine.
Austin Lippert, the owner of Aternex LLC, does the work himself, from the first call to the code in production. AI agents are tools he uses, under his review.
I use AI agents every day, and how they touch your data is agreed per project. Claude and Codex work on code and tasks that involve no private data. When data has to stay private, I run agents through zero-data-retention endpoints, where the provider keeps nothing, or on models that run entirely on local hardware, where it never leaves the machine.
Rates are agreed per engagement, after I see the details of the work. The price follows the scope, which is agreed in writing before work starts.
I reply within two business days. A booked call skips the wait: pick a time on the calendar.
Yes, around Knoxville, Oak Ridge, Kingston and Lenoir City. Everywhere else, the work is remote, anywhere in the US.
Yes. Most requests are for contract work, but a full-time W-2 role is just as welcome when the work fits: modernizing legacy code and databases, or building a new product end to end.
Yes. On contract or on staff, Austin works in the languages, tools and process your team already uses. His defaults are .NET and TypeScript, and he moves the stack you have toward its current long-term support release.
Book a time that suits you and describe the system and what is wrong with it. If it is a fit, the next step is access and a measurement; if it is not, you will hear that plainly. I reply within two business days.