Writing the code isn’t the hard part. Everything around it is.

VrittOS is an AI software delivery platform that takes a product idea through the whole lifecycle: brainstorming, a business requirements document (BRD), design mockups, epics and user stories, AI-generated code delivered as GitHub pull requests, AI-generated tests with a self-healing fix loop, and release documentation. You approve every stage; AI does the heavy lifting.

Once you approve the backlog, developer agents implement each user story on a feature branch in your connected GitHub repository and open a pull request — never a direct push to main. The PR includes the implementation, generated tests, test results, and a summary. Your team reviews and merges like any other PR, and your CI runs on it.

No. VrittOS removes the repetitive delivery work — writing specs, decomposing backlogs, scaffolding, boilerplate implementation, test upkeep, release docs — while humans keep every decision: four approval gates (requirements, BRD, design, backlog) plus code review on every pull request. Small teams ship like bigger ones; nobody merges code unseen.

Yes. Start a project from an existing GitHub repository and VrittOS reads the code and writes the documents it implies — an as-built requirements document, an architecture document, a design system if there is a UI, and a backlog of what already exists with the files behind each item. You review and correct the requirements before approving; from then on "Add a feature" plans new work against your existing code. The scan is priced by repository size (20, 40 or 80 credits by source-file count), quoted for free before anything starts, and refunded if it fails.

GitHub is required for code generation: you connect a repository and all code arrives as pull requests there. Jira is optional: approved epics and stories are created in your Jira project with acceptance criteria, priorities, and status sync. Both use scoped OAuth tokens you can revoke at any time.

Credits meter AI work — for example generating the story backlog or implementing a story as a pull request each costs a fixed number of credits. Builder (£29/month) includes 300 credits and 5 active projects, Startup (£99/month) includes 1,000 credits and 10, and Growth (£399/month) includes 5,000 credits, alongside team-seat limits. Project limits count what you are running at once — archive a project to free a slot and nothing is deleted — and monthly project add-ons raise the number you can run simultaneously. If you run out mid-month, top-up packs start at £12 for 100 credits (larger packs cost less per credit, down to £400 for 5,000) — you never need to change plan just to finish a story.

Every new workspace starts with a 14-day free trial and 100 AI credits — no credit card required to begin. That is enough to take an idea through planning, documentation and a first story end to end. When the trial ends you move to Pay as you go: your projects stay exactly where they are, and you buy credits whenever you need them rather than committing to a subscription. Add a payment method at any point to move onto a plan with a monthly allowance — Builder includes 300 credits a month, 5 active projects and Jira sync.

Pay as you go is where your workspace lands when a trial or a subscription ends — there is no monthly fee and nothing is switched off. Your projects, documents and repositories stay exactly where they are, and you buy credits when you have work to do. It suits irregular delivery: freelancers and consultants who ship in bursts rather than every week. Credits do the limiting instead of a subscription, so you only pay when you are actually building. A plan is worth it once you are building regularly — it adds a monthly credit allowance, more projects running at once, more seats, and Jira sync.

VrittOS generates unit and integration tests alongside every implemented story. When CI fails, a triage agent reads the actual failure and pushes a corrective commit to the same branch, then re-runs CI — a bounded loop that stops and asks a human if it can’t converge. Failures get fixed before merge instead of accumulating as QA debt.

Your code stays in your GitHub repositories, accessed with scoped tokens. Data is encrypted in transit and at rest on Microsoft Azure infrastructure. We do not train AI models on your code or data — model providers are used under terms that exclude training on API inputs. See our Security page for the full picture.

Yes. Upgrades take effect immediately; you can cancel any time and keep access until the end of the paid period, after which you drop to Pay as you go rather than losing your workspace. Unused monthly credits don’t roll over, but purchased credits stay available.

It gets picked up rather than left for you to find. A story that fails is retried, and if it fails again you get a fix run explaining what broke and what it proposes. Pull requests whose CI passed before the base branch moved are refreshed and re-checked before anything merges, so a green tick always describes the code that is actually going in. If something is wrong with the delivered app, you report it from inside VrittOS and it comes back as a pull request you review. And if a story is still stuck after all of that, one click hands it to a real person on our team, with the diagnostic detail already attached — free, on every plan.

VrittOS monitors its own delivery pipeline for runs that loop or fail repeatedly. When it finds one it stops the run before it spends more, pauses the affected work, and calculates exactly what the failure cost you — and we return those credits. You do not have to notice it or ask.

Yes, with Flutter — one codebase that ships to both iOS and Android. Design mockups are generated on a phone canvas rather than a desktop one, and the same delivery pipeline applies: stories, branches, tests and pull requests. Native-only Swift and Kotlin projects are not supported.