Skip to main content

FAQ & Troubleshooting

Common questions and solutions for Quome Studio.

Quick Problem Solver​

Jump to your issue type: Click through the sections below to find specific solutions for your problem area.

Getting Started​

Account & Organization Setup​

Q: How do I create my first organization?

A: An organization is automatically created for you every time you create a new Quome Studio account. There's no need to manually create one - your organization will be ready to use immediately after signup.

Q: Can I belong to multiple organizations?

A: Yes! You can be a member of multiple organizations and switch between them using the organization selector in the top navigation.

Billing & Pricing​

Q: What's included in the Prototype Plan?

A: The Prototype Plan ($100/month) includes everything you need to build and deploy compliant applications:

FeatureWhat You Get
App Deployments2 active applications
Storage1 GB included
SecurityHIPAA-ready architecture
IntegrationAuto-commit to GitHub
SupportEmail support + comprehensive documentation
AccessTutorials and community resources

Q: Is there a free trial?

A: Yes! A 14-day free trial is available to explore all features and evaluate the platform.

Q: Can I upgrade or cancel anytime?

A: Absolutely! You can upgrade to enterprise plans or cancel your subscription at any time. Changes take effect at your next billing cycle.

Q: What about enterprise needs?

A: For larger teams or custom requirements, we offer enterprise solutions with custom pricing. Contact us for App-as-a-Service, Agent-as-a-Service, and other professional services.

Using Quome Studio​

Application Development​

Q: What makes a good prompt for Quome Studio?

A: Follow the 4-step framework for best results:

  1. Goal: Clearly state what you want to build
  2. Return format: Specify the type of application (web app, API, etc.)
  3. Warnings/constraints: List any limitations or requirements
  4. Context: Provide relevant background information

Example:

Goal: Build a patient management system for a small clinic
Return format: Web application with user authentication
Constraints: Must be HIPAA-compliant, handle 50 concurrent users
Context: Clinic has 3 doctors, needs appointment scheduling and medical records

Q: How do I improve my application after initial creation?

A: You can iteratively improve your app:

  1. Go to "My Apps" page
  2. Click "Edit with AI" on your application
  3. Use specific prompts to add, modify, or remove features
  4. Test changes in the preview environment
  5. Deploy when ready

Q: Can I customize the generated code?

A: Yes! You can:

  • Download the source code for local customization
  • Use GitHub integration for version control
  • Make direct code edits (with deployment via existing app images)
  • Combine AI generation with traditional development

Deployment Issues​

Q: My application failed to deploy. What should I check?

A: Common deployment failure causes:

  1. Resource Limits: Check if your app exceeds memory/CPU limits
  2. Port Configuration: Ensure your container exposes the correct port
  3. Environment Variables: Verify all required secrets are configured
  4. Image Size: Large container images may timeout during deployment
  5. Database Connections: Check database credentials and network access

Q: How long should deployment take?

A: Typical deployment times:

  • Small applications: 30-60 seconds
  • Medium applications: 1-3 minutes
  • Large applications: 3-5 minutes
  • First deployment: May take longer due to image pulls

Q: My app deployed but returns 500 errors. How do I debug?

A: Check the application logs:

  1. Go to your application dashboard
  2. Click "Logs" to view real-time application logs
  3. Look for error messages, stack traces, or startup issues
  4. Common issues include missing environment variables or database connection failures

GitHub Integration​

Debugging Quokka
GitHub integration troubleshooting information.

Setup & Configuration​

Q: Why can't I see the GitHub option in my project?

A: GitHub integration requires:

  • A Quome Studio application already created
  • Appropriate permissions in your GitHub account
  • Organization admin role (for organization repositories)

Q: Which GitHub account should I connect?

A: Connect the GitHub account where you want to store your code. This can be:

  • Your personal GitHub account
  • A GitHub organization where you have admin permissions
  • Multiple organizations (you can grant access to all during setup)

Q: Can I disconnect from GitHub later?

A: Yes, you can disconnect GitHub integration:

  1. Go to your project settings
  2. Navigate to "Integrations"
  3. Click "Disconnect" next to GitHub
  4. Your code will remain in GitHub, but sync will stop

Sync Issues​

Q: My changes in Quome aren't showing up in GitHub

A: Check these common issues:

  1. Sync Status: Look for sync indicators in the Quome interface
  2. Branch: Ensure you're looking at the correct branch (usually main)
  3. Permissions: Verify Quome has write access to your repository
  4. Network: Check if there are any connectivity issues

Q: I made changes in GitHub but they're not in Quome

A: Currently, Quome only supports unidirectional sync (Quome → GitHub). Changes made directly in GitHub won't sync back to Quome. This feature is planned for future releases.

Q: Can I use GitHub Actions with my Quome project?

A: Yes! Since your code is in a standard GitHub repository, you can use GitHub Actions for:

  • Automated testing
  • Custom deployment workflows
  • Code quality checks
  • Security scanning

API Integration​

Troubleshooting Quokka
API troubleshooting and error resolution guide.

Authentication Issues​

Q: My API calls are returning 401 Unauthorized

A: Common authentication problems:

  1. Expired Token: Check if your Bearer token has expired
  2. Wrong Header Format: Ensure format is Authorization: Bearer YOUR_TOKEN
  3. Invalid Token: Verify the token is copied correctly
  4. Wrong Authentication Method: Some endpoints require session cookies instead

Q: How do I generate a new API key?

A: To create an organization API key:

curl -X POST "https://demo.quome.cloud/api/v1/orgs/{org_id}/keys" \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -d '{"name": "My API Key", "ttl_sec": 7776000}'

Q: My API key stopped working suddenly

A: Check these possibilities:

  1. Expiration: API keys have configurable TTL (time to live)
  2. Revocation: Organization admin may have revoked the key
  3. Organization Changes: Key may be tied to an organization you no longer access
  4. Rate Limiting: You may have exceeded API rate limits

Common API Errors​

Q: Getting 404 errors for valid endpoints

A: Verify:

  • Base URL: Ensure you're using https://demo.quome.cloud/api/v1
  • Organization ID: Check that the organization ID in the URL is correct
  • Resource Existence: Verify the application/secret/resource actually exists
  • Permissions: Ensure you have access to the requested resource

Q: 403 Forbidden errors on API calls

A: This usually indicates permission issues:

  • Organization Access: Verify you're a member of the target organization
  • Role Permissions: Check if your role allows the requested action
  • Resource Ownership: Some resources can only be accessed by their creators

Performance Issues​

Application Performance​

Q: My application is running slowly

A: Performance optimization tips:

  1. Resource Allocation: Check if you need more CPU/memory
  2. Database Queries: Optimize database connections and queries
  3. Image Size: Smaller container images start faster
  4. Caching: Implement appropriate caching strategies
  5. CDN Usage: Use CDN for static assets

Q: My app crashes with out-of-memory errors

A: Memory troubleshooting:

  1. Check Logs: Look for memory-related error messages
  2. Resource Limits: Verify your container's memory allocation
  3. Memory Leaks: Review code for potential memory leaks
  4. Upgrade Plan: Consider upgrading to a plan with more resources

API Performance​

Q: API calls are taking too long

A: Improve API performance:

  1. Pagination: Use pagination for large result sets
  2. Filtering: Apply filters to reduce data transfer
  3. Geographic Location: Consider geographic proximity to servers
  4. Rate Limiting: Ensure you're not hitting rate limits
  5. Batch Operations: Group multiple operations when possible

Security Questions​

Access & Permissions​

Q: How do I rotate API keys?

A: Best practice for API key rotation:

  1. Generate a new API key with appropriate TTL
  2. Update your applications to use the new key
  3. Test that everything works with the new key
  4. Delete the old API key
  5. Monitor for any failed authentication attempts

Q: Someone left my team. How do I revoke their access?

A: To remove team member access:

  1. Go to organization members page
  2. Find the user and click "Remove"
  3. Rotate any shared API keys they may have used
  4. Review audit logs for their recent activity
  5. Change any passwords or secrets they had access to

Data Security​

Q: Where is my data stored?

A: Quome Studio data storage:

  • Application Code: Stored in secure, encrypted repositories
  • Application Data: Stored in isolated, encrypted databases per organization
  • Secrets: Encrypted with AES-256 and stored separately from application data
  • Logs: Encrypted and retained according to your data retention policy

Q: Can Quome staff see my application data?

A: No. Quome implements zero-knowledge architecture where:

  • Your application data is encrypted and inaccessible to Quome staff
  • Code and secrets are encrypted at rest and in transit
  • Only you and your authorized team members can access your data
  • Support staff can only access system logs and metadata (not your data)

Need More Help?​

When to Contact Support​

Contact support@quome.site if you experience:

  • Security Issues: Any suspected security problems
  • Data Loss: Missing applications, secrets, or data
  • Billing Problems: Payment or subscription issues
  • Complex Integration: Custom setup or enterprise requirements
  • Unresolved Issues: Problems not covered in this FAQ

What to Include in Support Requests​

  • Clear Description: What you were trying to do and what happened
  • Steps to Reproduce: Exact steps that caused the issue
  • Error Messages: Copy the full text of any error messages
  • Screenshots: Visual context when helpful
  • Environment Details: Browser, organization ID, timestamp
  • Impact Level: How this affects your work or business

Emergency Support​

For Enterprise customers with critical issues:

  • Production Down: Use emergency escalation procedures
  • Security Incidents: Email security@quome.site immediately
  • Data Loss: Contact support with "URGENT" in subject line
  • Compliance Issues: Immediate notification required

Additional support is available by contacting the support team at support@quome.site for issues not covered in this guide.