App Kit / Dev Console
Build and deploy on the instance. Ask, review the diff, preview, then ship.
Product screens recreated with synthetic data.
src/intake only. The kit checkout is read-only. The hold goes in gate.js, with a test beside it. This is the instance I checked before touching a file. Nothing deploys until you click Merge & Deploy.Click the map, a service, or + to add workers, runners, or a GPU task. The tour plays until you do. On an instance those counts are real. Here they only change the picture.
App Kit is the foundation: a URL, a database, and a layer repo that is yours. Dev Console is the product on that foundation. At /dev a team asks for a change, reads the plan, reviews the diff, opens a preview, and deploys — frontend, backend, or rules — to UAT, then promotes to production. The loop stays in one console.
The agent works the layer repo only. The kit you rent stays read-only. A browser workspace is there if you want to edit by hand. Pipeline design is still nQube, and a workflow write is still agentOS. This console changes your application and ships it, under your review.
Dev Console is not nventr Agent and it is not agentOS. The agent here edits a repository and you deploy that change. nventr Agent talks on a page. agentOS commits a workflow write. Do not expect this screen to compile an iOS binary or to post a journal entry.
A team that rented an instance because they are building an app, and wants the change loop — plan, diff, preview, deploy — inside that instance.
App Kit, at /dev. Platform Team does not include an instance, a layer repo, or this console.
Pricing →Synthetic example. Not a customer.
You ask for the invoice form to hold anything over $10,000. The agent plans the change against the layer repo and returns a diff. You read it. A preview runs the form. You merge and deploy the frontend to UAT. Production is a separate promote. The kit image you rent is untouched. The pipeline that posts invoices, if you have one, is still an nQube graph — this deploy did not create it.
The agent’s writes land in the layer. The rented foundation stays read-only.
Nothing from the agent merges unseen, and nothing deploys until you say so.
Frontend, backend, and rules are separate targets. Production is a promote, not the first click.
A fix, a feature, or a refactor, against your layer repository. The plan comes back before the edit.
The work comes back in the console. You are the gate.
See the change running before it merges.
UAT is the landing zone. Production is a promote you make on purpose. Frontend, backend, and rules are separate targets.
App Kit is the instance — large files, heavy jobs, health checks on every deploy, updates that stay out of your layer. Dev Console is how you change that layer.