Frequently Asked Questions

Everything you need to know aboutguided engineering.

Clear answers on code privacy, live advisory calls, pricing scope, and how we resolve technical blockers for AI-built apps.

Orvatos provides guided engineering consultancy for AI-built applications. We help founders diagnose bugs, resolve deployment issues, improve performance, review security concerns, and make their software more reliable. We explain the proposed changes and guide you through implementation and testing.

No. Our standard guided consultancy does not require repository access or a full-codebase upload. We work with you through a live consultation, using relevant screens, error messages, logs, or carefully selected code snippets when needed. Please do not share secrets or sensitive information.

You retain ownership and control of your codebase. We ask you to avoid displaying credentials, API keys, private keys, customer data, or other sensitive information during consultations. We handle information shared with us according to our applicable confidentiality and data-handling terms. We explain these terms before work begins.

That's okay. You can share what you know about your application, the tools you used to build it, and the issue you're experiencing. If you're unsure about your programming language, database, or hosting provider, tell us that. We'll help you identify the relevant details where possible.

First, submit an intake request with basic information about your application and the issue. We review your request and discuss the scope, deliverables, and price with you. During the consultation, we investigate the problem, document proposed changes in your client dashboard, and seek your approval before proceeding with the agreed implementation guidance.

Our standard service is guided consultancy. We explain the necessary changes and help you implement them in your own environment, using step-by-step instructions or AI coding prompts where appropriate. You remain in control of your repository and decide when to apply changes. Any different delivery arrangement must be agreed upon separately.

Pricing depends on the nature of the issue, its complexity, and the work required. After reviewing your intake request, we'll propose a scope, deliverables, and price before you commit. Standard service packages may be introduced as our offerings develop.

We test changes against the agreed acceptance criteria and document the findings. If the issue persists or a related defect appears during the agreed validation period, we'll review it against the original scope and explain the next steps. Additional work outside the agreed scope may require a separate estimate and approval.

Yes. We can help with development-stage problems, configuration issues, database integration, authentication, deployment preparation, and other technical blockers. Tell us your application's current stage in the intake form so we can determine whether your issue fits our services.

If you believe a credential has been exposed, revoke or rotate it promptly and review relevant access logs where possible. We recommend avoiding the display of credentials and sensitive files during screen sharing. We can help you identify appropriate next steps, but you remain responsible for managing your accounts and credentials.

Your dashboard records the issue details, proposed changes, approvals, and relevant testing outcomes. We ask you not to include passwords, tokens, private keys, or unnecessary sensitive data in these notes. The applicable retention and deletion policy explains how engagement records are handled and when they may be removed.

Have a specific architectural challenge?

Get personalized guidance for your tech stack

Submit your intake with your issue description. Our team reviews each request within 24 hours.