About
A platform company, not a portfolio
Novaryn builds AI operations for other businesses. The 2 products it runs itself are not the business — they are the proof that the platform underneath works in production.
Every AI vendor can demonstrate an agent doing something impressive once. The difficult part is the year after: tenant isolation, approval gates, budget ceilings, retries, an audit trail, and a credential store that survives an employee leaving. Novaryn is that layer, and the agents on top of it.
The products it runs itself — TechHub.cafe and CardCopilotAI — exist because building the platform against real users is the only way to find out which parts of it are fiction. Everything shared is real code with tests: a design system where a product's entire identity is one number, a theme engine an administrator drives without a deploy, and one identity, RBAC and billing layer underneath.
Who builds it
Novaryn is built by Abdul Qadir Khan. That is the whole team, which is the reason the leverage argument above is not an abstraction — it is the only way the work fits.
If you want to talk about any of it, the address is aqadirkhan93@gmail.com.
Where it stands
The design system, theme engine and domain kernel work today and have test suites. So does the runtime: a resumable agent loop, a model gateway with budget caps and cross-provider failover, hybrid retrieval over pgvector, a workflow engine, and an approval layer that holds a run mid-flight until a person decides. Every table carrying customer data has row-level security enabled and forced.
Not everything is built. There is no MCP client, no evaluation runner, and no billing. Some connectors are written against a vendor's documentation and have never touched their servers, which is a different thing from working and is labelled as such in the code. The changelog keeps that current, and the demo is a real run rather than a mock-up.
Principles
Four decisions everything else follows from
Build the expensive part once
Identity, governance, design, AI plumbing — every product needs them and none of them is the product. Building each once is what makes a small team able to ship at all.
Constraints beat discipline
A design system that relies on people remembering the rules drifts within a quarter. So the rules are structural: off-system colours do not compile, contrast is solved by the ramp rather than chosen, and reduced motion is one variable rather than a media query in every component.
Say what is built
Plans are labelled as plans on this site, in the docs, and by the assistant. It is tempting to describe a roadmap in the present tense, and it costs exactly the audience worth having.
Products stay independent
Each product owns its repository, its schedule and its users. The platform is adopted, never imposed — which means each piece has to be independently worth adopting.
Next
Talk to the person who built it
One address, answered directly. Partnerships, a technical question about the token architecture, or press.