ProjectCode

What ProjectCode is

ProjectCode is an AI app builder for full-stack web apps. You type what you want, and the platform produces a React frontend, a NestJS backend, a database schema, migrations and live APIs, then tests and deploys the result. The site labels the product BETA and pitches it at startup founders who want a working MVP in front of users quickly, as well as developers and product teams, each of which has its own solutions page. The pages do not say where the company is based.

What you build and how

The home page frames the flow as Prompt, Plan, App, Deploy. A prompt box offers starting types: web app, landing page, dashboard, CRM, website and internal tool. It also shows a model picker that reads "Claude Sonnet 5", and example prompts such as "A CRM with leads, deals and a dashboard" and "A SaaS billing portal with Stripe". Describe the product in plain language and the AI turns it into a plan covering pages, models, routes and auth decisions. The site puts that step at about 12 seconds.

Next comes a preview of the React interface running real service calls against a seeded mock adapter, plus a review of the generated backend plan (about 90 seconds on the site's timeline). Every build then gets a staging URL with seeded data, where you click through real flows and refine the app with follow-up prompts before going live (about 40 seconds). The final step flips the mock adapter off, runs migrations and smoke tests, and ships Docker containers to an Ubuntu VPS behind NGINX with TLS (about 25 seconds). The page describes the contract between frontend and backend as typed API contracts verified against real routes, and it says "No mock arrays".

Versioning is part of the pitch. The site says every build is versioned and that you can roll back to any previous version in one click, with code, schema and deploy reverting together. Its demo terminal shows a rollback restoring all three in 8 seconds with no downtime, which reads as an illustration rather than a guarantee.

The startups page lists what a first build includes. User accounts, sessions and data storage are ready from day one, so you are not wiring up auth before you have validated anything. Every project is deployed to a shareable live URL the moment it is built, which the page suggests sending to investors, advisors and early users. Iteration happens by conversation: you describe the change and the AI applies updates across the full stack, which the page presents as the answer to painful pivots in a tightly coupled codebase. That page also lists a waitlist landing page as a typical first project, and it carries comparison pages against Lovable and Bolt.new.

The ticketing page shows how far a single prompt can reach. Its sample prompt asks for a platform for a concert promoter running 100 events per year with up to 10,000 attendees each. The prompt lists a seating map builder for assigned seating, ticket tiers (Floor GA, Seated, VIP), Stripe payment at checkout, QR code tickets delivered to email and Apple or Google Wallet, a fan-to-fan resale marketplace capped at 2x face value, box office POS for walk-up sales, group sales with invoice billing, season passes, a mobile scanning app with offline mode, and a post-event analytics report. The page says a project like this takes 2 to 4 hours to build. Sibling pages cover online booking and scheduling, event management and sports club management, so the same approach is offered across many business types. The site's own gallery of apps built with ProjectCode includes Board Pro, a Kanban task manager, plus Coffee Hub, Portfolio Pro, PlanSpace, Originalframe and TaxComply Pro, labeled as web apps or landing pages.

Integrations are described as a connectors section. The home page says 61 integrations ship with every app, spanning databases, payments, AI models, email, auth, storage and hosting. Stripe appears in the example prompts and PostgreSQL appears in the connector strip.

On deployment, the ticketing page lists 4 options. Managed hosting is a one-click deploy to a live URL managed by ProjectCode. A custom domain connects with auto-provisioned SSL via Cloudflare. GitHub export pushes the code to your repo so you can self-host or deploy via Vercel, Railway or AWS. Docker export gives you a Dockerfile and docker-compose for any containerized environment. The startups page adds that you can export clean, readable code and hand it to an engineering team, promising no platform lock-in.

What the pages say about cost, limits and scale

Pricing is token-based. The ticketing page shows 3 entries.

• Free costs $0 and lists live preview, managed hosting and full code export.
• Token Packs start from $5, and the page says purchased packs roll over every month.
• Enterprise is custom and lists custom models, an SLA, SSO and private cloud deployment for large teams.

The page also says there are no per-seat fees and no vendor lock-in, and that pricing "scales with your usage". It does not publish how many tokens a $5 pack holds, how many tokens a typical build uses, or any cap on the Free tier, so you cannot work out a monthly bill from the pages alone. Calls to action repeat "Free to start" and "No credit card required".

Scale claims sit on the home page under a "Live metrics" heading. The site reports 1200+ apps shipped across teams this month, 21k+ frontend-to-backend API contracts verified, and an average build time of about 4 hours per one-shot build. These are the company's own figures and the pages do not explain how they are counted.

On skills, the startups FAQ answers "Do I need to know how to code to use ProjectCode?" with no. It says the product is designed for non-technical founders who can describe what they want in plain language, and that technical users can go deeper. The pages show no security or compliance certifications, no support channels and no customer count beyond the figures above. SSO is mentioned only as an Enterprise item.

Who it suits and who it does not

A solo founder or small startup team with an idea and no backend engineer is the clearest fit. The pitch is a live, testable app in hours, with auth and a database already in place and the code exportable once an engineering team arrives. Developers who want a head start on a conventional stack, with a repo they can push to GitHub and run on their own infrastructure, get the Docker and GitHub routes. Agencies and product teams can use the ticketing, booking and event examples as starting prompts for client work.

There are caveats. The output is one stack, React with NestJS, so a team committed to a different backend language is not the audience. The product carries a BETA label, and the pages publish no uptime commitment outside the Enterprise SLA mention. Token pricing is flexible but unpredictable until you have seen how many tokens your own builds consume, and the pages give no usage figures to estimate from. A team that needs strict compliance evidence will have to ask the company, because none is published on these pages.