Internal tools that match the workflow
Trackers, intake, queues, and dashboards in the language of ops. Not a generic kanban skin. Columns, statuses, and notifications named in the prompt.
CodeLoom for enterprises
Ship the tool in the meeting, not the quarter after.
Prototype faster, validate with a running app, and put internal software in front of the people who asked for it — without waiting on an engineering queue that already has a roadmap.
Same day
First clickable preview
One project
Product, design, ops
Export
When IT wants the repo
Whop
Cards never hit CodeLoom
What this is
A factory for frontends the team can click.
CodeLoom is not a slide generator and not a no-code island. Cursor writes production TypeScript into a project on this host. Preview is Vite. Export is a zip. That is the whole pitch, expanded.
Prototypes that survive the meeting
A clickable product the room can argue about. Restore if the next prompt wrecks a screen. Publish only if you want a public Community card.
Campaign and product sites
Landing pages and product marketing as real React, not a website builder theme. Export when brand wants to host elsewhere.
Sales demos that exist
Walk a prospect through software with their nouns in it. Keep a project per account so last week’s demo does not leak into this one.
Build together without the bottleneck
Product writes the journey. Design names type and space. Ops names the statuses. One chat, one tree, one iframe. Nobody waits for a “can you mock this?” thread that dies in Slack.
ProductDesignOps
Same project · Can edit
Intake · waiting on legal
Approved · notify Slack
Done · export zip
The loop
01
A brief, not a ticket storm
Write the job the way the team already talks: who files it, who approves it, what stuck looks like. The agent lands routes and screens in stages.
02
Review in a running app
Preview is Vite on this host, proxied into the studio iframe. Stakeholders click empty states instead of commenting on a PDF of mocks.
03
Steer the same files
Follow-ups edit the tree Monaco already shows. Restore a checkpoint if a prompt goes sideways. Mention @path to attach a file.
04
Handoff without a rewrite
Export a zip of TypeScript. Secrets stay in the studio ciphertext store — you add production env on your side.
Controls we will put in a review
Full notes live on /security. This is the enterprise cut.
Identity
Email, hashed passwords, httpOnly sessions. Google and GitHub when those keys are on the host. Seats and SSO are a conversation, not a silent checkbox.
Secrets
Project secrets are ciphertext. They do not belong in chat. Generated apps only see what you put in their env after export.
Network
Preview binds localhost. The sandbox allowlists npm/node. It will not sudo your estate.
Payments
CodeLoom Pro checkout is Whop. Card data never hits this app. Webhook HMAC updates plan. Register the webhook URL in Whop.
Ops
/admin is off the public nav: IPs, sessions, users, projects, runs. Email allowlist or unlock password after sign-in.
Honesty
We do not paste NVIDIA on this page as if they bought a seat. When a company lets us name them, we will.
Who this page is for
Questions procurement asks
Is this a design tool or a codebase?
A codebase. Vite + React + TypeScript in a workspace you own. The iframe is that app running.
Can we run it in our VPC?
Export the zip. This studio is the factory on etzelchicko.com. On-prem of the factory itself is an Enterprise conversation, not a self-serve toggle.
How do seats work?
Projects are owned by the signed-in account today. Business is a higher token cap on one account. Named seats, SSO, and a DPA are what a demo is for.
What is Pro vs Business vs Enterprise?
Pro is $19.99/month via Whop card checkout. Business is $99/month for a higher cap. Enterprise is procurement, security review, and how you want the factory to run for a team.
Where does data live?
Accounts and project metadata in our database. Files on this host. Telemetry for the operator. Community publish is public on purpose.
How do we start?
Create an account and run a real brief in the studio — that is the demo. Or write us from /sign-up after you have seen preview work.
See the factory, then talk.
A working preview beats a deck. Create an account, run an internal brief, then we can talk seats.