
NamiQ
Contact salesActively maintained
not read yet
Use
- For
- Founders, CTOs and engineering leads with inherited or AI-built software, and small firms without IT staff.
- Price
- Contact salespricing page, read Oct 26, 2026
- Activity
- Actively maintainedsite updated 2 days ago
- Company
- NamiQ LLCsite footer
- Used for
- Map an inherited system nobody understands
- Stabilize software whose fixes keep breaking other parts
- Build a defined new scope with a delivery record
- Has an MCP server (1 in the registry)public registry →
- Publishes llms.txt, a file written for AI assistantsnamiq.io ↗
Contact sales
- HeadquartersAustin, USper their site
- Run byNamiQ LLCsite footer ↗
- Their AI providers train on itYessecurity page ↗
- Privacy policy updated2026-10-03privacy policy ↗
“What bounds it is scope, retention and use, and each of those is something you can write into the contract: only the repositories you name, nothing of yours retained past the working copy, nothing of yours used to train a model of ours, and the hosted provider named in the contract together with its data terms.”
security page ↗
These are NamiQ's own statements, read from its pages. We did not audit them. A line that is missing was not found on the pages we read; it does not mean the practice is absent.
- MCP serverio.namiq/latticeverified in the MCP registry
- Stateanswers, 7 toolschecked 2026-10-26
- Address to connectlattice.namiq.io/mcp
This card as JSON, for your agent →
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
Figure and bar: visits/mo, estimate · year: online since
- #1

Qodo
Performs code review across pull requests and development workflows with full codebase context and enforced quality rules.
14.6kActiveFrom $30/mo - #2

Daemons by Charlie Labs
Runs always-on AI processes defined in markdown files that automate recurring tasks across Slack, Linear, and GitHub without prompts.
68ActiveFrom $50/mo - #3

ContinuumMCP · open
Senior engineer available on retainer to build, ship, and maintain products for founders.
26ActiveFrom $500/mo2005 - #4

UptimelyMCP · sign-in
Runs minute-by-minute uptime checks, pages on-call engineers after two failures, and publishes a customer status page.
6ActiveFrom $29/mo - #5

SpiderbrainMCP · sign-in
Builds a versioned dependency map from source code and documents, showing what a change breaks before it ships.
6Active - #6

VulXMCP · sign-in
Keeps a labelled history of changes your coding AI makes to your app, with checks, live versions and undo checkpoints.
2ActiveFrom $39/mo
Not it? Say what you need
betaThree tools from the Atlas for the job you describe, each with what fits and what does not.
No notes yet. What do you use NamiQ for?
Sign in to leave a noteWhat is NamiQ?
Delivers and maintains software builds for clients, with a recorded check trail for every change, using AI roles reviewed by people. It is listed in the Atlas under Developer tools and made by NamiQ LLC.
Who is NamiQ for?
Founders, CTOs and engineering leads with inherited or AI-built software, and small firms without IT staff.
How much does NamiQ cost?
NamiQ does not publish prices; its pricing page says to contact sales (2026-10-26).
Is NamiQ free?
No. Its pricing page showed no free plan on 2026-10-26.
Do people use NamiQ?
Little sign of use.
Is NamiQ still maintained?
Actively maintained: site updated 2 days ago.
Who owns NamiQ?
NamiQ is run by NamiQ LLC, per its site footer (2026-10-26).
Does NamiQ train AI on your data?
Its security page speaks for its AI providers rather than for NamiQ itself (2026-10-26): “What bounds it is scope, retention and use, and each of those is something you can write into the contract: only the repositories you name, nothing of yours retained past the working copy, nothing of yours used to train a model of ours, and the hosted provider named in the contract together with its data terms.”
What are alternatives to NamiQ?
In Developer tools, by use: Qodo, Daemons by Charlie Labs, Continuum, Uptimely, Spiderbrain, VulX.
How we read a tool
No votes, no reviews, no vendor claims. Every week a crawler reads each tool's own site and a few public registries, and the words on the card are bands over what it read.
- Use: visits to the site (estimated), installs from npm and PyPI, presence in Chrome's usage report.
- Activity: the newest release on GitHub, npm or PyPI; the newest dated page on the site; open roles on a public jobs board.
- Price: the vendor's own pricing page, read with the date. A figure is printed only when it is on that page.
- The line and the use cases are written by us from the homepage, one tool at a time, and refused when they repeat the vendor's marketing.
How AI assistants read each site — the reading vendors ask us about — is on each tool's own visibility page.
How we read every tool → · By INITE Atlas Desk
Cookies
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.