I What Anvyr Is
Anvyr is a software company. We build our own products and we build software to order.
When a client comes to us, we learn their domain first, then build the right thing from scratch. We don't reskin templates, we don't outsource, and we don't hand off half-finished work. The same standard applies whether the product has our name on it or someone else's.
We make software for people who read source code before they read landing pages. Our users don't want magic. They want leverage.
II Principles
1 Intention over convention
Every name, every architecture, every default is a deliberate choice. We do not cargo-cult patterns from other codebases. If a decision cannot be explained in one sentence, it hasn't been thought through enough.
2 Fast with precision
We move fast. We ship often. A bug doesn't wait until Monday. An email doesn't wait until next week. Urgency is the default, not because we're reckless, but because delays are a form of disrespect. Speed without precision is chaos. Precision without speed is irrelevance. We refuse both.
3 Code is craft
Software is a creative discipline. Every function signature, every error message, every line break is a design decision. We treat them that way. The codebase is the product, not just the output of the product.
4 Ship, then sharpen
We do not polish in private. We ship early, we ship often, and we improve relentlessly in the open. A feature that exists and works today beats a perfect feature that exists next quarter. But "ship fast" is not an excuse for shipping broken. Everything that leaves the door must function correctly. We iterate in public, not in committee.
5 Explain nothing twice
Good software doesn't need a manual. Good architecture doesn't need a diagram. If the user has to read documentation to understand a basic workflow, the workflow is wrong.
6 Speed is respect
Fast software respects the user's time. We do not ship loading spinners where instant response is possible. We do not add startup screens. We do not waste cycles. This applies to products and to how we operate: response times, turnaround, decisions. Waiting is a choice, and we choose not to.
7 Own the stack, or own nothing
When we depend on something, we understand it completely. When we build something, we build it from the ground up if the alternatives don't meet our standard. We don't wrap bad abstractions in pretty APIs. We replace them.
III Structural Constraints
These are not guidelines. They are governance decisions, designed to survive growth, leadership changes, and external pressure.
Permanent Private Structure
Anvyr will never go public. No IPO, no SPAC, no direct listing. Ever. Public markets create legal pressure to maximize quarterly returns, which is incompatible with building software with intention. We fund growth through revenue and aligned capital. The company answers to its users and its craft, not to shareholders demanding exits.
Naming
Names are permanent. They carry identity. Anvyr project names are constructed, phonetically sharp, and intentional. They are not acronyms, not descriptions, not inside jokes. A name should be pronounceable in any language and memorable after hearing it once.
Quality gate
Nothing ships without the author being willing to defend every line. "It works" is not a quality bar. "I'd build it this way again" is.
Open by default
We build in the open when possible. Not because open source is a strategy, but because building in public forces honesty. Code that can be inspected is code that has to be good.
IV What Anvyr Is Not
We are not a body shop. We don't place developers at desks and bill hours. When we take on client work, we take ownership of the outcome.
We are not optimizing for growth metrics. Revenue matters because it funds the work. The work is the point.
We are not slow. If it looks like we're waiting, something is wrong.
V On Working With AI
AI is a tool in the workshop, not the carpenter, not the client. We use AI to amplify craft, not to replace judgment. Every AI-assisted output is reviewed, understood, and owned by a human. If we can't explain why the code is right, we don't ship it.
We believe AI and humans build better software together than either does alone. The human provides intent, taste, and accountability. The machine provides speed, breadth, and tirelessness. The result is software neither could have built alone.
This document is a living artifact. It evolves as Anvyr evolves, but the core never changes: build things that work, for people who care.