San Diego studio. Work across the United States.

Cyriac Zeh founded Nidrosoft in San Diego after design and engineering roles at Anthropic, Microsoft on Bing and Edge, Intuit, and Gap Inc. The studio name is the company. The AI Architect is the practice he ships under when the job is an end-to-end product: design, code, and a live system in your stack. Both names belong to the same person in the same city.

San Diego is also where the public speaking happens. The San Diego Executive Roundtable is a recurring panel with regional operators on generative AI, data, cloud, and the future of work. A Southern California CXO session in La Jolla put him on a stage with people from Qualcomm, Philips, LPL Financial, the US Navy, and the UKG Workforce Institute. AI for the Rest of Us ran here and on a livestream. Those rooms are local. The builds are not limited to the county.

If you searched for an AI partner in Los Angeles, Dallas, Boston, or Atlanta, you still land here. We did not cut the country into city pages. A separate URL for every metro would pretend we staff each one. We do not. The person you meet on the audit is the person who writes the first integration, and that person works from San Diego unless the embed needs him on a plane.

Twelve-plus years of product work sit behind that sentence. The public archive lists 16 systems. The studio count across client and own products is 125 shipped. Those numbers live on this site so a US buyer can check them before a call, not after a pitch deck.

Operators type city names into search because that is how buying starts. A fund in Manhattan, a dealer group in Houston, a clinic group in Phoenix, a software team in Seattle. The work those teams need is rarely a local retainer. It is a map of how tickets, intake, inventory, or spend already move, then a system that runs inside those tools.

This page is the answer for all of them. Pacific, Mountain, Central, and Eastern time are the four clocks we plan around every week. Alaska and Hawaii book the same audit and get the overlap written into the first note. A team in Miami and a team in Portland, Oregon, buy the same method. The difference is the hour we pick for standups and whether someone needs to fly.

We name cities here only so you can find yourself. New York, Boston, Washington, Atlanta, Miami. Chicago, Minneapolis, Detroit. Dallas, Austin, Houston, Denver. Seattle, Portland, the Bay Area, Los Angeles, San Diego. Secondary markets book the same way. If your company is registered in Delaware and your people sit in three states, say so on the form. The audit is built for that shape.

What we will not do is publish a fake office in each of those places. Nidrosoft does not have a New York studio, a Texas studio, or a Seattle studio. Cyriac lives in San Diego. When a week on site is the right move, he travels. When video and shared accounts are enough, we stay on the wire.

Most United States work starts on a Google Calendar audit, then moves into your Slack, Teams, or email and the tools you already pay for. Cyriac sits with the people who do the recurring job: the coordinator who copies the same fields, the buyer who hunts listings after hours, the engineer who cannot see which feature ate the model bill. That sitting can happen on a shared screen. It can also happen in a break room if the work only makes sense in person.

Travel is for the embed, not for theater. A dental group that wants Omnira-style intake watched at the front desk may need a few days on site. A dealer group that wants overnight outreach in the spirit of Nexuvo may need a morning on the lot so we see how cars actually arrive. A software team that already lives in Linear and GitHub rarely needs a flight. We say which it is after the audit, not in a packaged tour.

English is the working language. Documents, tickets, and training stay in the words your team already uses. If a department runs on Spanish at the counter, we design the interface and the handoff around that, still with an English owner for the build. We do not invent a bilingual practice we do not staff.

The five steps on /how-we-work are Embed, Diagnose, Scope, Build, and Own. In the US that usually means two weeks to cost the recurring work, a short strategy pass to pick the first system, then a build window measured in weeks, not a year-long transformation slide. Larger companies start in one department with an internal sponsor. Teams under 30 people fit when a single build pays for itself. The band we spend the most time in is 30 to 250 people.

• Audit on Google Calendar, or write cyriac@nidrosoft.com if a slot does not exist for your coast
• Access only to the systems you approve, under your policies
• Build in your Azure, AWS, Google Cloud, Cloudflare, or private setup
• A person on your side who can run the system after the first ship

Embed means we go into the company. A discovery deck that never watches a real ticket is a different product. We watch how a claim, a lead, a mix, or a purchase order actually moves, including the spreadsheet nobody put in the architecture diagram.

Diagnose means every recurring task gets hours, feasibility, and payback. You get a ranked map, not a list of models. Scope means you buy an outcome: what runs itself, what a person still approves, what it is supposed to save. Money, contracts, and customers stay under a human decision. That rule does not change because the buyer is in California or because they are in Ohio.

Build means the system goes live in the CRM, inbox, ERP, or app you already run, with someone in-house pairing so the knowledge is not trapped in a contractor. Own means there is nothing theatrical to hand over. It was yours from the first commit in your accounts. We stay on for what you ask and stay out of the rest.

US teams often already have a tool sprawl: Salesforce or HubSpot, a helpdesk, a billing system, two model vendors, and a shared drive that still wins. The job is to pick the first workflow that pays back and wire it so your people can see the trail. TokenTra exists because software teams could not see which feature burned the tokens. That is the kind of visibility we aim for on client builds as well.

Healthcare work on this site has a name: Omnira Dental, live at omnira.dental. It is agentic software for dental practices, built around the way a clinic already runs intake, follow-up, and the front desk. If you operate medical or dental offices in the United States, that is the artifact to inspect. We follow the access rules, business associate terms, and retention policies you already have. We do not sell a studio-wide healthcare certification.

Real estate work has Eviction Wizard at evictionwizard.ai: notice to writ in one dashboard. US property operators who still chase the same packet through email can see a finished path. Automotive work has Nexuvo. Dealers using that system pull in three times more private-party inventory with about 80 percent less manual outreach, because the hunt and the first contact run overnight across the marketplaces they already watch.

Software teams get TokenTra at tokentra.io. Teams there cut 10 to 30 percent of wasted AI spend once the bill is visible by feature. Music and media get Octana at octana.one, one message in and a finished video out, and MixGuidera, which reads a track and suggests EQ, compression, and effects. The method behind those products is the method we bring to a US company in any of those industries.

Venture, manufacturing, FinTech, e-commerce, and professional services are listed on the industries hub because the same embed works there. Protectron is a public system aimed at EU AI Act paperwork. A US company that sells into Europe can look at it. A US-only team can ignore it. We will not bolt a compliance product onto a job that does not need one.

Production systems run in the accounts you already own, or in accounts we set up under your name. Microsoft Azure, AWS, Google Cloud, Cloudflare, private infrastructure, and more than one tenant are all in the how-we-work list because those are the rooms US companies already rent. We do not ask you to move the company onto a mystery Nidrosoft cloud.

Approved access and audit trails are part of the residency list. If your counsel wants every write logged, we build that. If a model is allowed to draft and a person must send, we build that. If a healthcare or finance policy already names who can see a field, we stay inside it. The studio does not publish a SOC 2 report, and we will not imply one.

Plenty of United States companies still hold EU personal data: a London subsidiary, an Irish entity, a customer list that includes France. When that is true, EU hosting and EU data residency are on the table, the same sentence we use for European buyers. When the data never leaves the US, we keep it in the region you name. The audit is where we write that down, with your lawyer in copy if you want them there.

State privacy rules (California CPRA and the growing state list) are your policies to name. We implement the retention, deletion, and access path you already promised customers. We do not sell a privacy program as a stamp. NanoBrief is a studio example of speed, briefs in under two minutes against a three-hour habit, and even that product still leaves the human as the person who sends the brief.

What we need from your side before code

A named owner, access to the tools the work already uses, and a workflow that repeats. If legal needs a vendor form, send it to cyriac@nidrosoft.com and say which coast should review it first. If security wants a list of subprocessors the build will touch, we write that list against your stack, not a generic appendix.

Cyriac Zeh takes the first call. That is the design engineer who founded the studio, the person behind The AI Architect, and the one who will either write the integration or sit next to the engineer who does. There is no account layer between a US operator and the work. If the job later needs a specialist we trust, we say so and you still own the repo.

He is in San Diego, on Pacific Time, and reachable on the calendar product already embedded on /contact. LinkedIn, Instagram, and X are public if you want a face before you book. The about page has the career line, the products (Omnira, Octana, Eviction Wizard, Guidera, TokenTra, Protectron, Nerlude, and the rest of the live list), and the principles: start with the person doing the work, take the difficult parts, build for the way the business already runs, keep people in control.

US buyers sometimes want a bench of twenty. We are a studio. The trade is speed and a single thread from constraint to production. If you need a hundred-person implementation army in four time zones next Monday, you should buy a different firm. If you need one working system in a department this quarter, this is the seat.

Training is a separate offer when a leadership room or an engineering pod needs a half-day on their own tools. We have run office hours for small business and live builds from messy intake to a front-office system. Those sessions are useful. They are not a substitute for a build if the job is a live workflow.

Book a free audit on the Google Calendar slot on the contact page. Pick a time that works on your coast. Eastern teams usually take a morning slot so it is still morning in San Diego. Pacific teams can use the afternoon. If every slot is wrong, email cyriac@nidrosoft.com with your timezone, the system you want touched first, and who will be in the room. We reply within a day.

Bring one messy workflow, not a tour of the whole company. Intake that dies in a shared inbox. Inventory that depends on someone refreshing marketplaces at 10pm. A model bill nobody can split by feature. A notice packet that lives in four folders. We will tell you whether a workshop, a scoped build, or a longer program is the next buy, and we will tell you if you should stay with a tool you already have.

The form on /contact asks for first name, last name, work email, company, and what you are exploring. That is enough. You do not need a request for proposal written like a federal bid. If procurement requires one, send the template and we will fill the parts that are true: San Diego, Nidrosoft LLC, Cyriac Zeh, the public systems, the method.

• Who owns the workflow after we leave
• Which systems we may log into, and who approves that
• Whether anyone must be on site for the first watch
• Whether any data in the workflow is EU data that needs EU hosting

Code, prompts that matter, and the wiring into Salesforce, HubSpot, ServiceTitan, Dealership CRM, or the homegrown app all live where you can revoke our access. Your team gets the documentation and the pairing time to change a field mapping without opening a ticket to San Diego. We will stay on a retainer if you want ongoing improvement. We will also leave.

Expectations on the method page are blunt. You work directly with the people building it. You get something the floor can use on a Tuesday. You keep control of what we build. Those sentences were written for this country first. They still apply if your parent company is abroad and the operating team is here.

If the first system works, the same method moves to the next team. That is the transformation offer: audit through builds, training, and rollout, team by team, until your people run it. It is still one studio, still one thread, still no invented regional HQ.

Guidera is a live iOS travel companion in the archive. Helia, Nerlude, Protectron, and the rest of the live list show that the studio keeps shipping its own products so client work is not the first time a pattern has been tried. US buyers can click those URLs. They are not case studies with the names removed.

A board-only strategy mandate with no build is a poor fit. A team that only wants ChatGPT seats and a prompt pack can buy those from the toolkit list on the about page, or from a dozen other places, without an embed. A company that needs a partner on site five days a week in three cities should hire locally or buy a firm that staffs that way.

If your only measure of progress is a slide for a quarterly offsite, we will bore you. If your measure is a live process with a number attached (hours back, inventory in, spend down) we have public systems that already carry those numbers. Nexuvo and TokenTra are the ones we quote because they are live, not because they flatter every industry.

International subsidiaries of a US company should still start here if the operators sit in the United States. If the operators sit in London, Amsterdam, or Singapore, use those region pages. The studio does not change. The clock and the hosting sentence might.

If you are a United States operator with a repeating workflow and a person who can own the result, book the audit. Say the city you sit in, the tool the work already lives in, and whether you want Cyriac on site for the first watch. Nidrosoft will answer as the San Diego studio. The AI Architect is the name on the work that ships.