Bayon AI logo
BAYON AI
Back to services

Request a project review

Give us the product context, the current risk, and the next milestone. We’ll determine whether a production-readiness assessment or a focused Vibe Fix is the right starting point.

Start with context, not credentials

This form is only for the initial fit review. It asks for enough information to understand the product without opening your source code or production systems.

Structured review

We evaluate the product stage, primary risk, and next milestone before requesting code access.

No secrets or Git access yet

Repository collaboration belongs to stage two, after the engagement boundary is clear.

Compare the services

Tell us about the product

Required fields help us assess fit. The Git repository is intentionally not requested here.

Describe the behavior, affected users, and what you have already tried.

Do not include passwords, API keys, customer data, repository invitations, or other secrets. Source access comes later, after the review scope is confirmed.

Submit your product in two stages

Start with enough context to confirm fit. Share source access only after the review scope is agreed.

  1. Request an initial review

    Use the dedicated project-review form to introduce the product, the current problem, and the outcome you need. No source access is needed at this stage.

    • A short description of the product and who uses it.
    • The live product or demo link, if one is available.
    • What is breaking, slowing down, or creating the most risk.
    • Your current deployment status and the next milestone you need to reach.

  2. Share the project securely

    Send the Git link and grant repository-level access to GitHub user toledoroy. Most products use one repository, but the review follows the product boundary rather than repository count.

    • Reply with the Git repository URL after Bayon AI confirms the review.
    • Invite GitHub user toledoroy as a repository collaborator with only the access needed for the review.
    • Include the main branch, setup instructions, deployment link, and known failure or scaling concerns.
    • Remove collaborator access when the assessment or engagement is complete.
Return to the project-review form

Keep secrets out of the handoff

Do not send or commit passwords, API keys, .env files, production credentials, signing keys, or customer data. Use sanitized setup values and the narrowest repository access required for review.