Manus developer help · Agent-built web apps
Fix your Manus-built app.
An autonomous agent built the whole thing: front end, back end, database, sign-in, even payments. A senior engineer reads what it wrote, fixes what real users would hit, and makes sure the code is yours.
Photography is illustrative.
- Built by
- The Manus agent, which plans and builds the whole project from a goal
- Back end
- Manus's built-in database, server code, file storage and email sign-in
- Hosting
- Manus, on Google Cloud Run: autoscale by default, or one always-on reserved instance
- Code
- Full download, or export to a private GitHub repository with two-way sync on main
Who this is for
For founders whose app was built by an agent, and who now need to know what is in it.
Manus works differently from chat-led app builders. You describe the goal, and an autonomous agent plans and builds the whole project: front end, back end, database, sign-in, and Stripe payments set up in a sandbox. Manus then hosts it, with custom domains and free SSL.
That is a great deal of software made with few moments where a person saw the decisions. The result usually works, and nobody has read it. That is where we start: reading the code the way a new senior engineer would on day one, then fixing what real users and real money would find.
Failure modes
The ways Manus-built apps go wrong.
These are what we look for first in a web app the Manus agent built. Some come from the hosting Manus documents; most come from code that has not yet had a human review.
-
Code nobody has read
- What you see
- The app works, but nobody can say how, and every change is a guess.
- What is actually wrong
- An agent that builds the whole project in one run makes hundreds of decisions on its own. Nothing is wrong with that until the first change, when nobody knows which parts depend on which.
- How we fix it
- A review that maps the architecture, the data model and every place money or personal data flows, then tests around the critical paths before anything changes.
-
Slow first requests and dropped connections
- What you see
- The first visit after a quiet spell is slow, or live updates and chat features drop.
- What is actually wrong
- Manus's default autoscale hosting has cold starts after inactivity, and its documentation does not recommend persistent connections in that mode. Each instance has 1 vCPU and 512 MB, with up to five instances.
- How we fix it
- Reserved mode where the app needs it, features designed for the hosting they run on, and a load test before launch.
-
Signed in is not the same as allowed
- What you see
- Sign-in works, yet a user who changes an ID in a request sees someone else's data.
- What is actually wrong
- Manus builds email and password sign-up, login and sessions. Which records each user may read and change is still the app's own code, and generated routes often check only that someone is logged in.
- How we fix it
- An ownership check on every server route that reads or changes data, enforced on the server, with a test for each.
-
Payments set up, not yet proven
- What you see
- Test purchases work in the sandbox; nobody has tried a renewal, a failed card or a cancellation.
- What is actually wrong
- Manus configures Stripe automatically, with a sandbox, products and subscriptions. Going live, and handling every event in a subscription's life, is where the edge cases are.
- How we fix it
- Every Stripe event the app relies on handled on the server and verified, subscription state used to decide access, and each case tested before the switch to live keys.
-
A GitHub connection that breaks quietly
- What you see
- Changes in GitHub stop reaching Manus, or the other way round.
- What is actually wrong
- Manus exports to a new private repository with two-way sync on
main. Renaming the repository or transferring it to another owner breaks the connection, and disconnecting stops the sync, although you keep the repository. - How we fix it
- The repository left where Manus expects it, developer work on branches merged by pull request, and a check that both sides match.
-
Hosting limits nobody planned for
- What you see
- The bill or the response times change as real users arrive.
- What is actually wrong
- Each account gets a monthly credit shared between hosting and the database, and autoscale instances are small. A launch can outgrow both.
- How we fix it
- A capacity estimate from your expected traffic, the hosting mode chosen on purpose, and a recommendation on whether to stay or move.
Before you hire anyone
What to try yourself first in Manus.
- Get a copy of the code now. Manus lets you download the entire codebase, front end and back end, at any time, or export it to a private GitHub repository. Do one of them before anything else.
- Roll back the bad edit. Manus's site says it tracks the changes it makes and lets you roll back to a previous version. Go back to the last one that worked rather than asking the agent to repair forward.
- Check with two accounts. Create two test users and try to see the first one's data while signed in as the second. If you can, stop and fix that before launch.
- Try reserved mode. If cold starts or dropped live connections are the problem, the always-on reserved mode removes cold starts.
- Test the whole payment life in the sandbox. Buy, renew, fail a card and cancel before switching to live keys.
- Leave the repository where it is. Do not rename or move the GitHub repository Manus created; that breaks the sync.
How we work
How we work on a Manus app.
Manus's documentation says you can download the entire codebase at any time, and export it to a private GitHub repository that syncs both ways on main. We work in that repository, on branches merged by pull request, so the project keeps working in Manus.
Whether the app stays on Manus hosting is a decision we make with you after the review, with what a move would involve spelled out first.
-
A free 20-minute call
You show us the Manus app and tell us what is going wrong. We say what we expect to find, and whether a paid check is worth it yet.
-
Quick Security Check or App Readiness Review
A senior engineer reads the code and tests the running app: data access, keys, sign-in, payments, deployment.
You get Every finding in writing with its severity and fix; the review adds a keep, change or replace call for each part and a fixed quote.
-
Fixed-price fixes
Security & Data Hardening from $7,500, or Production Launch from $15,000, in your repository, with a test beside each fix.
-
Handover
Production kept apart from development, a deploy you can roll back, and notes so you, the tool or any developer can carry on.
Prices
Where to start, and what it costs.
-
App triage call
Free
20 minutes
-
Quick Security Check
$495
Delivered in 48 hours. The fee is credited toward the App Readiness Review.
-
App Readiness Review
$1,500 flat
5 business days. The fee is credited toward any fix booked within 30 days.
Fixes are priced after the check or review, at one fixed price before anything starts. The full price list and how fees are credited.
Proof
Who does the work.
A US software engineering firm. The founding team has taken a product off an AI app builder before (built, not yet in paid use) and runs a production telehealth platform on Supabase. We are an independent firm, not a Manus partner or agency. Across the systems the team built and runs:
- 20,900+ automated tests across the systems the founding team built and runs
- 16,800+ CI runs automated builds and test runs on GitHub Actions
- 940+ merged pull requests across the same codebases
Counted from the repositories and CI history of the systems the founding team built and runs, 22 Sep 2026; each figure rounded down. How we counted
Questions buyers ask
Manus questions, answered.
Can you work on an app the Manus agent built?
Yes. Under the agent it is ordinary web code, and we read it like any codebase we take over: architecture, data model, money and personal data first.
Can I keep using Manus after you fix it?
Yes. We work in the GitHub repository Manus syncs with, and add automated checks every change must pass, including the agent's.
Should I move it off Manus hosting?
Not by default. We look at your traffic, features and costs and recommend staying or moving, with the reason, and what moving would take.
Will you rewrite everything?
Rarely. The review marks each part keep, change or replace, with the reason, before any work is priced.
Are you affiliated with Manus?
No. Oracis is an independent US software engineering firm. We fix and finish apps built by Manus, alongside apps from Lovable, Replit, Cursor and other tools.
What does it cost to fix a Manus app?
The first call is free. The Quick Security Check is $495 and its fee is credited toward the App Readiness Review, which is $1,500 flat and credited toward any fix booked within 30 days. Security & Data Hardening is from $7,500 and Production Launch from $15,000, each at one fixed price set after the review. We never bill hourly on work nobody has sized. The full price list.
Send us the Manus app.
The app link or the GitHub repository, what worries you, and when real users arrive.