Product updates, improvements and decisions from the team building Zorentia.
Releases
32
Field notes
4
Latest
Added a guided Project Library project for teams ready to bring engineers into their product. It covers connecting the product, preparing for Office Hours, handing over an implementation directive and planning the next cycle.
The work itself continues in Zorentia Office. The guide tracks where you are, and its helper stays grounded in the Office instructions instead of suggesting another platform.
Define Your Product Idea now gives each answer an Idea clarity score out of 100, built from four parts: focus, specificity, context for the reader and convincing detail.
The written feedback still explains what is holding the score back and how to strengthen the answer. The score measures clarity, not whether the idea has been validated.
Debug Your Code now works like the other guided Build Studio tools, with GOAT Helper on hand and the conversation saved with your session.
The guide is free to start and repeat, and finished guides can be reopened.
Added a guided domain project that turns your business context into a shortlist of names and a decision plan, then walks you through checking availability and price, registering, verifying and securing the domain, and planning renewal.
A finished plan can be shared through one private link. Whoever opens it can follow the same steps without an account, and the link can be replaced or revoked at any time.
Project Library projects now save your answers, generate the finished piece and let you edit, preview and download it, starting with a portfolio website.
Coaching now reads every answer you have already given, so later questions build on earlier ones instead of asking for the same facts twice.
The helper in each step now recommends only the tools that step uses, so a presentation or spreadsheet project is no longer pointed at website hosting.
Feature Builder now sits in Build Studio under After launch, where a product already exists for it to build on.
Each feature specification is written from your actual system, naming its real data and routes instead of describing the feature as if it were built from nothing.
Downloaded packages now include a verification report for each stage, showing what was checked across architecture, database, backend and frontend, and what was not.
Each package also includes a README explaining the folders, entry points, how the frontend, API and database connect, and how to run it locally.
Frontend Generator now builds screens from a versioned library of tested components instead of free-form HTML, so generated screens connect to the backend the same way in preview and in export.
Forms can now offer choices loaded from your own data, such as subjects, categories or teams, as a dropdown.
Signup now confirms every builder is 13 or older without asking for a date of birth, and paid accounts for 13 to 17 year olds go through a guardian.
Published idea pages are now private links only. They stay out of search engines, are no longer listed in a public Explore feed, and can be reported.
Public feedback forms no longer collect names or email addresses from the people who respond.
Build Studio needs a computer, so visitors on a phone can now email themselves a link to finish signing up on their computer instead of hitting a dead end.
The link only opens signup with the email filled in. It does not create an account or carry a login.
Know What Features to Build is now a guided evidence check. Describe one feature per row and it is checked against the customer evidence you collected, with the reason a feature is or is not supported.
Clear statuses, retries, delete confirmations and session recovery mean a paused check never leaves you stuck.
Published a dedicated High Schools pathway showing how students move from an idea to a working application while learning product judgement, system design, testing, and launch decisions.
Added clear year-level pathways, teacher cohort visibility, program pricing, and implementation guidance so schools can evaluate and run the experience with confidence.
Added team access so account owners can invite a collaborator to work across the same ideas, projects, Build stages, and credits.
Each collaborator receives separate, revocable access, giving owners control without sharing their own account key.
Frontend Generator now builds interfaces screen by screen, reducing long-running generation failures while keeping the complete product flow connected.
Backend Generator now assembles completed work into a downloadable package even when non-blocking project warnings remain, with the README and Goat Helper ready to guide the next step.
Added a persistent feedback action inside Build Studio so builders can report a problem, confusing step, or feature idea from the workspace where it happened.
Relevant tool and project context can travel with the submission, while failed messages stay in place so nothing has to be written twice.
Strengthened Architecture generation so each feature carries an exact, verified connection between its data, backend functions, and screens.
Introduced durable Database Designer workspaces with recovery for interrupted work, downloadable SQL and validation artifacts, and an exact handoff into Backend Generator.
Expanded MVP planning beyond a single foundation feature, so builders can scope the full end-to-end journey their first release must deliver.
Carried that complete first-release scope into Architecture, Database, Backend, and Frontend generation so later stages build from the same product intent.
Added a dedicated pitch-deck workspace with slide previews and PDF export, turning an early product idea into a presentation ready to share.
Improved public idea pages with a live preview and a clearer feedback flow, so builders can put an idea in front of people before committing to the build.
Added a guided Deployment Advisor that considers the project stack, budget, audience, expected usage, and maintenance horizon before recommending where to host an application.
Builders can describe the project or select its folder for stack detection, then keep the resulting recommendation in their decision history.
Expanded the organization workspace so program leads can see student activity, current Build stage, remaining credits, and recent access in one place.
Added cohort filtering, student moves, access management, and roster export for day-to-day program administration.
Rolled out a unified design system across the entire platform, so every tool, dashboard, and page now looks and behaves consistently.
Rebuilt the interface from reusable components, making the product faster to navigate and easier to learn.
Refreshed the landing experience to match the polish of the product itself.
Introduced auto-subscribe billing so builders and cohorts stay active without manual renewals.
Launched organisation support with seat allocation, so programs and institutions can manage a whole cohort from one account.
Added single-invoice cohort billing for faculties and departments.
Introduced a Program Lead view for managing members and access.
Released the Publish feature, turning a builder's plan into a polished, shareable public page.
Added an archive so every output stays organised and reviewable over time.
Shipped the "Should I Build This" tool and a revamped MVP scoping flow to help builders pressure-test an idea before committing.
Launched Extend, a dedicated workspace for adding new features to an application you have already built.
Built-in Build and Verify steps guide each new feature from idea to working code.
Shipped Build: a guided, chat-driven flow that takes a builder from intake to generated, production-ready code.
Launched dedicated experiences for High Schools and Universities, mapping the build process to coursework and programs.
Released a VS Code extension for the architecture assembler, bringing Zorentia into the builder's own editor.
Introduced conversational, guided intake across the tools, so builders are coached through each step instead of facing a blank form.
Reorganised the code generation stages into a single, sequential workbench, giving builders one clear place to move from data to backend to frontend.
Rebuilt the generation engine on an asynchronous backend with background workers.
Large builds now generate dependably in the background instead of blocking on a single long request.
Added high-fidelity screenshots and video walkthroughs to the guided build stages.
Users can now see exact feature layouts and output styles before starting a build.
Every plan now includes a visual "End State" preview to ensure alignment with your project goals.
Added detailed "How it works" and "Best use cases" sections to the discovery flow.
Introduced "Who it's for" context to help builders identify the right path for their specific technical background.
Refined landing page copy to better communicate the Zorentia mission and target personas.
Updated build-stage names to be more direct and outcome-oriented.
Improved copy across the site to make deliverables explicit and easy to understand.
Integrated "How it works" modules throughout the site to assist users at every stage of the build process.
Integrated Codex as a local development plugin to streamline the transfer of code from Zorentia to your codebase.
Codex now automates the heavy lifting of file and folder structuring.
This update makes it significantly easier for builders to move from the Zorentia dashboard to a functional local environment.
Dramatically expanded the step-by-step guidance for deployment and infrastructure stages.
Moved from high-level summaries to explicit, granular instructions to ensure a 100% completion rate across all backgrounds.
Goal: Provide a "no-fail" path to deployment that requires zero external support.
Introduced a lock on build-stage regeneration to ensure credits are used effectively on new ideas.
Added explicit documentation within each plan to ensure builders understand the roadmap before they commit.
Updated credit pricing for backend and frontend generation to be based on the number of screens.
This ensures the investment scales accurately with the amount of production code and infrastructure being generated.
Database generation remains a flat 2 credits, while logic and interface generation now reflect the complexity of the project scope.
Linked all dependent stages (4, 5, 7, 8, and 9) directly to the Stage 3 MVP Scoper.
This architectural change ensures that every build is consistent and prevents missing details in the later stages of the chain.
Builders now select from their verified MVP scorecard to ensure a thorough and stable system build.
Made the Free Tier explicit on the pricing page to show new builders exactly how to get started.
Simplified the pricing structure into a single, high-value tier designed specifically for the student and independent builder market.
Launched an Access Key recovery tool to ensure builders never lose momentum.
This makes the onboarding process fully self-serve and ensures urgent access is always available during the build process.
Launched the official Contact Page to provide a direct line to the team.
Added explicit contact information to assist builders who need immediate feedback during high-stakes launch moments.
We are committed to ensuring no build hits a standstill.
