Skip to content
AI-operated software and IT services

Build the software. Secure what it runs on. Keep IT running.

We build and maintain your software. We look after the IT and security it runs on, so a small firm does not need a team of its own. And when a new vulnerability lands, we read it against the vendor’s own advisory and write down what to do about it. Each of the three leaves a record you can check.

AI-operated delivery
Specialist AI roles do the routine work, so a small team can take on what would otherwise need a large one.
Human accountability
A Technical Architect owns what ships, and a Forward Deployed Engineer works with you and watches your running product.
Evidence at every step
The checks that ran, the decisions and why, and the board we ran it on are yours to keep and to check.

Our mission is to help small and mid-size businesses secure their IT assets, and to help startups afford fast, secure digital solutions for growth.

NamiQ LLC, Austin, Texas. Founded by Hung Trong Le.

Security, as a business decision

A new vulnerability is a question about your business. Here is how we answer it.

Not “how bad is the score” but “do we run it, who can reach it, what would it cost us, and by when”. In the ten CVEs we worked through on 28 October 2026 the score was a poor guide: a 2.7 was on the exploited list, and four unauthenticated 9.8s were not.

  1. 1Check
  2. 2Analyse
  3. 3Triage
  4. 4Act
  5. 5Prove
Every CVE ends in one of six places
  • Act now
    Exploited and reachable: mitigate in hours, patch inside the deadline
  • This week
    Serious, or exploited with a narrow reach: within seven days
  • Scheduled
    Real but not urgent: the next patch window
  • Track
    A precondition does not hold today: watch for change
  • Not affected
    Closed, with the evidence written down
  • Find out
    Unknown is not a state: inventory the asset today
The method from our CVE Triage Handbook. A person makes each decision, and writes the reason down beside it. The defaults are where we start, not rules; the handbook says what moves them.
What NamiQ is

We build and maintain your software, secure what it runs on, and hand you the evidence for every change.

A delivery service, not a tool

Nothing to install and no product to learn. We take a defined scope — a new build, a change to a system you already run, or one nobody understands any more — and deliver it.

Run by AI, owned by people

Twelve specialist AI roles do the work. A small team owns the outcome: a Technical Architect for what ships, and a Forward Deployed Engineer who works with you and watches your running product. Six checks decide what reaches your product, so speed does not come out of quality.

You keep everything, including the reasoning

Working software, every check that ran, the decisions and why they were made, and the board we ran it on. An ordinary repository, no proprietary runtime.
Four situations we take on

If one of these is yours, we have done it before.

You have something to build

The scope is clear and delivery capacity is the constraint.

You inherited something nobody understands

The author has gone, the documentation describes a version that no longer exists, and every change carries a risk nobody can size.

Nobody owns your infrastructure

No IT staff, a server someone else set up, and backups nobody has restored. Reviewed, set up once, then watched.

An AI tool built it, and now it breaks

You got to a working first version fast. Now each fix breaks something else, and nobody can say why.
What that produced · a case study of our own product

Our own product first, measured in public.

Read this first. One product, with the scope, the deadline and the stack chosen by us, and no client, procurement or change requests in the way. It shows how the factory runs. It does not show that your project will go the same way.

98%
Work completed
1,355 of 1,381 items closed
182/184
Features delivered
99% of the planned programme
2.64
Defects per 1,000 lines
every line shipped — within the 1–5 published for a disciplined team
17 days
To reach this scope
against a 9–18 month norm — see /results for the caveat

All of it, including the rework and queueing rows →

Who is behind it, and what we have done

Who we help, who runs this, and what we have done for them.

You are entitled to check us. Here is who runs this, what we are doing for clients as at 28 October 2026, and the work you can read without talking to anyone.

We help
Small and mid-size businesses
to secure their IT assets.
We help
Startups
to afford fast, secure digital solutions for growth.
Founder
Hung Trong Le
Formerly head of the embedded systems division, Hitachi Vantara Vietnam

Two decades building software for global clients in the United States, Japan and beyond, then five years building an AI business in Vietnam, before founding NamiQ LLC in Austin, Texas.

Hung Trong Le on LinkedIn
IT and security

An established, growing architecture firm in Austin, Texas, with eight to ten people, and a client since September 2026.

  • We are its IT department: laptop installation, Google Workspace administration and a help desk.
  • The help desk has a 2-hour first-response and 4-hour resolution target in business hours, written into the desk's service policy. They are targets, not guarantees.
  • Its shared drives, over a terabyte across ten drives, are copied every night to a disk on the firm's own network, and each run reports to a dashboard we watch.

As at 28 October 2026: the last nightly copy completed, with all 19 jobs ok and none failed.

Software delivery

DTLN, a paying client with a Socratic AI learning platform of about 147,000 lines, on a different technology stack from our own.

  • We take on enhancement and maintenance of an existing system we did not write.
  • Its material is the client's, so by default it is handled on local models only. Any exception is written down with who approved it and why, and every use is logged.

This is the engagement behind the factory's second codebase on our results page.

IT and security

Bootcivil LLC, a paying client since October 2026.

  • We manage its IT and security on the same service as our other IT client, supported through the same help desk.
  • We watch its estate using OCO, our cyber knowledge graph.

Managed since October 2026.

What you can read without talking to us

Counts are read from the Insights page as it stands, not typed. Where a source could not be read or two sources disagreed, the note says so.

Start where you are

The pages most people need, by the job.

This is not our claim. It is what 2026 published.

1.7×

more issues in pull requests containing AI-assisted code than in human-written code

arXiv preprint 2603.28592, March 2026
30–41%

rise in technical debt within six months of widespread AI tool adoption

Innovative Group, 2026
45%

of AI-generated code introduced a security vulnerability

Innovative Group, 2026
4×

maintenance costs by year two, for teams that do not actively manage the debt

Innovative Group, 2026

Published figures, directional rather than audited. Three of the four come from the same 2026 analysis; the first is a separate preprint. Every one is linked so you can weigh it yourself.

If you are building software · why it is hard to do well

Two ceilings nobody warns you about.

We wrote these in July 2026, from running a factory past 165,000 lines. The measurements since have pointed the same way.

Your reviewer is your throughput

AI can 10× how much code gets written. It cannot 10× how much a human can safely review. If every line still passes through one person's eyes, that person's reading speed is your real ceiling — no matter how fast the model is.

It degrades exactly where you are going

AI is excellent on day one: a blank file and an afternoon get you a week of senior work. Real products cross into six figures of lines, where parts depend on each other in ways nobody wrote down. The model does not get worse — the blast radius of confidently wrong grows with the codebase, and nothing tells you unless something is built to.
Generation capacity rises steeply while review capacity stays flat; the widening gap becomes unreviewed code.AI tooling adoptedmonths latervolumecode generatedcode safely reviewedthe gap shipsanyway
The gap is not idle work. It is code that ships having been read less carefully than the code before it. We think that is what the 1.7× figure is measuring, though the study reports the association and not the cause.
Why the usual answers fail

More generation makes it worse, not better.

Buy more AI tooling

It raises output and hands the review bottleneck straight back to the same people. The constraint was never how fast code gets written.

Hire senior engineers

Correct — and it costs you a quarter you do not have. The market for them is the reason you reached for AI in the first place.

Bring in an agency

A retainer team, and usually AI bolted onto the same process rather than changing it. Ask any supplier — us included — to show you the evidence for the last thing they shipped. Where each option wins →
What we do instead

Gates decide what ships. Not prompts, and not optimism.

Agents do the work; 6 checks decide whether it reaches your product. The last one asks whether a real person can finish the job on the running system — the failure tests cannot catch.

01

Understand

We read your problem — or your existing system — into a map of what it is, what depends on what, and where the gaps are. You get a plan you can challenge before anything is built.

02

Build

The work is split into small, tracked items with agreed acceptance criteria and assigned to the right specialist. Every change is isolated and reviewed.

03

Prove

Six checks run before anything reaches your product — ending with whether a real person can finish the job on the running system.

04

Report

Progress, quality and cost are recorded as the work happens. One live board, always current. Blocked work shows the day it blocks.

Insights

What we have learned running it.

All insights →

Start with one piece of work.

Give us one piece of work and read access to one system. We map it and come back with what we found, what we would build and what it would take, at no charge and before any commitment. About a week from read access to write-up. One service or repository up to roughly 50,000 lines; a larger estate we scope first rather than promise a week for.

Talk to us