FAQ & troubleshooting

This page collects the questions people ask most often, then walks through how to diagnose and fix common issues. If you can't find an answer here, contact support from your dashboard.

General questions

What is VibeCaaS? VibeCaaS — Vibe Coding as a Service — is a cloud development platform that combines AI-powered coding assistance, real-time collaboration, and seamless deployment. It gives you a complete environment to build, test, and deploy applications without managing infrastructure.

How is VibeCaaS different from other cloud IDEs? Deep AI integration (GPT-4, Claude, and Gemini), native GPU support for AI/ML workloads, built-in domain management, a template marketplace, and one-click deployment to multiple cloud providers.

What programming languages are supported? 30+ languages including JavaScript, TypeScript, Python, Java, Go, Rust, C++, C#, Ruby, PHP, Swift, and Kotlin — each with full IntelliSense and AI-powered completion.

Can I work offline? VibeCaaS is primarily cloud-based and needs an internet connection for core features. You can export projects for local development, and the desktop app offers limited offline capabilities for Pro and Enterprise users.

Account & billing

What pricing plans are available? Four tiers: Free (basic features, 1 project), Starter ($19/mo, 5 projects, custom domains), Pro ($49/mo, unlimited projects, team collaboration, GPU access), and Enterprise (custom pricing, dedicated resources, SLA). Paid plans include a 14-day free trial. See the pricing page for details.

Can I cancel anytime? Yes. Cancel from account settings — access continues to the end of the billing period, with no cancellation fees, and you can export your data first.

What is your refund policy? A 30-day money-back guarantee on new subscriptions. Contact support within 30 days for a full refund.

Technical questions

Where is my data stored? Code and project data live in encrypted, multi-region AWS S3 storage. Databases use Neon PostgreSQL or Supabase. Everything is encrypted at rest (AES-256) and in transit (TLS 1.3).

What are the container specifications? Default containers include 2 vCPUs, 4 GB RAM, 20 GB SSD, and 100 GB monthly bandwidth. Pro plans get 4 vCPUs and 8 GB RAM. Enterprise plans offer customizable resources, including dedicated NVIDIA T4/A100 GPUs.

What database options are available? PostgreSQL (via Neon/Supabase), MySQL, MongoDB, Redis, and SQLite. Each project can connect to multiple databases, managed or external. See Environments & secrets.

Security & compliance

How is my data encrypted? AES-256 at rest, TLS 1.3 in transit, and encrypted backups with customer-managed keys on Enterprise. Secrets and environment variables live in encrypted vaults with role-based access.

What compliance certifications do you have? SOC 2 Type II certified, GDPR compliant, and aligned with OWASP guidelines. Annual third-party audits, PCI DSS compliance for payments, and HIPAA-compliant environments on request for Enterprise.

How do you handle data privacy? Your code is never used for AI training, data is isolated per account with no cross-tenant access, you retain full ownership of your IP, and data export and deletion tools are provided for GDPR compliance.

Troubleshooting workflow

When something breaks, work through these steps in order:

1. Identify the problem — collect error messages, logs, and symptoms.
2. Reproduce the issue — build a minimal test case to isolate it.
3. Check recent changes — review commits and deployments that could be the cause.
4. Analyze logs — check application, server, and browser console logs.
5. Test solutions — apply fixes incrementally and test each change.
6. Document the fix — record the solution for next time.

Deployment issues

Deployment fails with a build error. Check package.json for missing dependencies, confirm all environment variables are set, clear the cache, and verify your Node.js version.

npm install --save-exact
npm audit fix
npm run build --verbose

Application crashes after deployment. Check the logs for the actual error, verify database connection strings, ensure the PORT variable is set, and raise memory limits if needed.

vibecaas logs --tail 100
vibecaas env:list
vibecaas restart

Database problems

Cannot connect to the database. Verify the connection string format, check firewall rules and IP whitelisting, and confirm SSL mode.

# Connection string format
DATABASE_URL=postgresql://username:password@host:5432/dbname?sslmode=require
 
# Test the connection
psql $DATABASE_URL -c "SELECT 1"

Queries are slow. Add indexes on frequently queried columns, use EXPLAIN ANALYZE to find bottlenecks, and add connection pooling.

EXPLAIN ANALYZE SELECT * FROM users WHERE email = 'user@example.com';
CREATE INDEX idx_users_email ON users(email);

Network & connectivity

CORS errors in the browser. Configure CORS headers on the backend and add your origins to the allowlist.

app.use(cors({
  origin: ["https://yourdomain.com", "http://localhost:3000"],
  credentials: true,
  methods: ["GET", "POST", "PUT", "DELETE"],
  allowedHeaders: ["Content-Type", "Authorization"],
}));

WebSocket connection fails. Enable WebSocket support in your deployment config, configure the reverse proxy for upgrades, and implement reconnection logic on the client.

Performance issues

The app runs slowly. Enable production optimizations, implement code splitting, use a CDN for static assets, and trim bundle size.

Memory leaks. Clean up event listeners and subscriptions, and always return a cleanup function from useEffect.

useEffect(() => {
  const subscription = api.subscribe(handleUpdate);
  return () => subscription.unsubscribe();
}, []);

CLI commands for diagnosis

Error code reference

Still need help?

If you can't resolve an issue, contact the support team from your dashboard — and check the status page first for any ongoing service issues. For background on the systems mentioned here, see Deploying your app, Environments & secrets, and the API overview.