Find unknowns
Surface ownership, security, testing, and operating questions that a working demonstration may not answer.
Free AI-built app readiness scorecard
Is your vibe-coded app ready for real users?
Answer ten practical questions about ownership, security, data, testing, deployment, recovery, and support. The result will identify a sensible next step without pretending that a browser quiz can certify an application.
What this can do
Turn “I think it is ready” into better questions.
Prioritize the conversation
Identify which areas deserve evidence before spending broadly on repairs, infrastructure, or a rebuild.
Choose a next step
Decide whether to keep preparing, request focused remediation, or begin with a structured technical review.
10 production questions
Check the foundation behind the demo.
Progress0 of 10
01 · Ownership
Does the business control the source repository, domain, hosting, database, and important vendor accounts?
Production should not depend on one person’s private account or an unclear copy of the source code.
02 · Environments
Are development, testing, and production separated with configuration managed for each environment?
Testing changes against live customer data or live services creates avoidable launch and recovery risk.
03 · Access control
Are authentication and server-side authorization verified for every important user role and privileged action?
Hiding a button in the interface is not enough. The server and data layer must enforce permissions.
04 · Data
Are data validation, tenant or customer separation, retention, deletion, and sensitive-data boundaries understood?
The team should know who can read and change each important record, including unusual and failure paths.
05 · Secrets and dependencies
Are secrets stored outside the source code and are important dependencies inventoried and reviewed?
Keys, tokens, packages, and third-party services need clear ownership, permissions, and update responsibility.
06 · Quality evidence
Can the critical user journeys and business rules be tested repeatedly with representative data?
A few successful demonstrations do not show what happens after a change or under an unexpected condition.
07 · Payments and integrations
Do payments, webhooks, email, external APIs, and background jobs handle retries, duplicates, timeouts, and failures?
External services fail in production. The app needs controlled behavior when they are slow, unavailable, or repeated.
08 · Release process
Is there a documented, repeatable deployment path with versioning, approval, verification, and rollback steps?
A production release should be observable and reversible instead of relying on direct edits and memory.
09 · Monitoring and recovery
Are useful logs, alerts, backups, restoration steps, and recovery responsibilities in place and tested?
A backup is only a promise until the team knows it can be restored within the needs of the product.
10 · After launch
Is one person or team accountable for hosting, incidents, maintenance, vendor changes, and continued development?
Production ownership should be agreed before customers discover who is responsible during the first failure.
Answer all 10 questions to see a planning result. Your answers stay in this browser and are not submitted to Honor Tech.
This educational scorecard is not a security audit, penetration test, compliance review, certification, warranty, or assurance that an application is safe to launch. A meaningful assessment requires authorized access to the actual application and its operating environment.
How to answer
Use evidence, not confidence.
Verified
Choose this when the control is documented, visible, or tested in the environment that matters.
Partial or unsure
Choose this when some work exists but the evidence, coverage, ownership, or production behavior is unclear.
Not in place
Choose this when the control is missing, inaccessible, undocumented, or has not been considered.
Common questions
Know what the score can and cannot tell you.
Can a score prove that my vibe-coded app is safe to launch?
No. The scorecard is an educational planning tool. It cannot inspect the source code, accounts, configuration, data, infrastructure, or actual application behavior. A meaningful production-readiness decision requires an authorized technical review of the real system.
Which AI-built app platforms does the scorecard apply to?
The questions apply to applications created with Lovable, Replit, Bolt, Cursor, v0, other AI coding tools, and conventional development processes. Production responsibilities come from the application and its operating environment, not only from the tool used to create it.
What should I do if I do not know an answer?
Choose Partial or unsure. An unknown answer is useful information because it identifies where ownership, documentation, testing, or evidence may need attention before launch.
Does Honor Tech receive my scorecard answers?
No. The score is calculated in your browser and is not submitted to Honor Tech. If you request a review, describe the project at a high level through the quote form and do not send passwords, API keys, production data, or other secrets.
A score is a starting point
Bring us the application when you need evidence from the real system.
Honor Tech can review the source, accounts, data boundaries, deployment, and critical workflows, then turn the findings into a prioritized production plan.