Services · Track IV · Custom development
When the box doesn’t fit.
The same studio that ships Midcore ships your project. Type-safe React. TypeScript. Python services. Rust where latency matters. On-prem deploys. Senior engineers without nearshore handoffs.
§ A · Engineering principles
Senior team. Type-safe. Handover-ready.
-
Senior engineers, no juniors hidden
Every engineer on your project has shipped to production for ≥5 years. No nearshore layering. No "junior under supervision."
-
Type-safety end to end
TypeScript strict. Rust where appropriate. Python with mypy. Schema-validated boundaries between every service.
-
Architecture custody
Every decision documented in ADRs. Every public interface versioned. Every migration evidence-chained.
-
On-prem if you need it
Docker, Kubernetes, air-gapped patterns. We have shipped to government and hospital environments.
-
Full handover
No vendor lock-in. Your team owns the code, the docs, the test suites, the deploy pipelines.
-
Code review with senior buy-in
Two-person review on every merge. No surprises in your codebase six months later.
§ B · Stack
What we reach for, by default.
Defaults are chosen because they have aged well. We will deviate when your situation argues for it — and explain why in writing.
Frontend
React 18, TypeScript strict, Tailwind, Astro for content-heavy work, Radix UI primitives.
Backend
Node + TypeScript, Python with mypy, Rust where latency matters, Postgres + pgvector, Redis.
Infra
Docker, Kubernetes, Terraform, Azure / AWS / GCP, air-gapped patterns for sovereign deployments.
AI plane
Midcore as the substrate; provider-agnostic via the LLM router; policy DSL on every tool call.
Observability
OpenTelemetry traces, structured logs, evidence chains, the runbook your on-call can actually use.
Security
Threat modelling per surface, secret rotation, SOC 2-aligned key management, audit-by-default.
§ C · Engagement model
Module, Surface, Programme.
Tier
Module
from $25k
A single bounded module — typed, tested, documented, integrated into your stack. 4–6 weeks.
Tier
Surface
from $80k
A complete product surface — frontend, backend, deploy pipeline, observability. 8–14 weeks.
Tier
Programme
from $35k/mo
Embedded senior team, multi-quarter horizon, co-ownership of architecture. For institutional builds.
§ D · Charter alignment
The instruments behind a custom build.
Every NeuroBazar engagement is anchored to specific Charter modules — each published with what it enables and what it regulates. This service leans on the instruments below.
-
⊕ AI Safety
No. 04
Runtime guardrails on every model call.
-
∎ Evidence Room
No. 10
Hash-chained audit of every AI action.
-
⌘ Governance Center
No. 12
Policy enforcement across every tenant, model, and surface.
-
✓ Approval Policies
No. 19
Consent paths that AI can read, follow, and never bypass.
-
◑ White-Label
No. 20
Your brand on the surface; sovereign over the substance.
§ E · FAQ
Questions, frankly answered.
- How many people are on the team that ships my project?
- Two to six. Always senior. We do not bring junior engineers under supervision; we do not nearshore. Concentration over headcount is part of our practice.
- Where does the IP live?
- With you. Every engagement starts with a clean IP assignment. The code is yours, the architecture decisions are yours, the deploy pipelines are yours. We retain the right to reference learnings publicly only with your written consent.
- Do you do fixed-price work?
- For Module engagements, yes — under $50k we will quote a fixed range and absorb scope drift within reason. For Surface or Programme tiers, we run time-and-materials with weekly transparency, because the variance is the value.
- Can we hire your engineers after the engagement?
- It happens. We do not block it; we ask for a 60-day handover overlap and a fair conversion fee. The conversion has happened three times in our history; we have parted on good terms every time.
- What languages and stacks do you refuse?
- We do not refuse stacks on aesthetic grounds. We do refuse engagements where the proposed stack is incompatible with the Charter — for example, surfaces designed to operate without consent vocabulary, or storage patterns designed to lock the customer in.
- What happens if the project goes sideways?
- We escalate inside our team in week one of trouble and to your sponsor in week two. We have stopped two engagements at week six of a planned twelve, returned the remaining budget, and parted on professional terms. We will not bill you to keep a doomed project alive.