Skip to main content

OXVO Builder overview

OXVO Builder is the AI app-building surface inside OXVO.

It gives teams a hosted workspace for creating apps from prompts, importing projects, iterating with AI Chat, reviewing live previews, connecting managed resources, publishing when ready, and improving from real product signals.

Builder is designed for product teams, founders, growth teams, support engineers, and developers who want to move from idea to working product without leaving the OXVO workspace model.

Build for day one​

OXVO Builder is not separate from the rest of OXVO. It is part of the same product loop:

  1. Build or import an app.
  2. Preview and refine it.
  3. Add support, Sessions, and product context.
  4. Publish or deploy when ready.
  5. Learn from support chats, replays, traffic, bugs, and usage.
  6. Improve the app with better context over time.

That means the app you build can live closer to the customer conversations, session evidence, and product signals your team needs after launch.

What you can do in OXVO Builder​

  • Start a new app from a prompt on Home
  • Import an existing GitHub repository
  • Work inside app-scoped AI chats with managed models
  • Choose build modes for quick edits, standard builds, advanced builds, and planning workflows where available
  • Review live preview, code, problems, security, Auto Improve, Cloud, and publishing state side by side
  • Select supported components in preview for targeted visual edits
  • Save reusable templates, prompts, and theme prompts for your workspace
  • Enable Builder Cloud when an app needs managed auth, database, storage, secrets, SQL, logs, or backend operations
  • Use Auto Improve when the app should learn from connected OXVO and OXVO Sessions signals
  • Connect GitHub and deployment tools when the app is ready for a production handoff

How Builder fits into OXVO​

Builder is launched through OXVO and uses the same workspace context.

That means:

  • there is no separate Builder identity model
  • workspace switching happens inside Builder
  • managed model access and Builder AI credits are controlled at the workspace level
  • apps, permissions, usage, billing, and plan access follow the OXVO workspace
  • support and session signals can be connected to Builder workflows when enabled

Use OXVO to govern the workspace. Use Builder to create and improve apps.

Connected product signals​

Builder becomes more useful when it has access to the product context around the active app.

Connected signals can include:

  • customer chats
  • support issues
  • replay behavior
  • session replays
  • traffic
  • bugs
  • errors
  • product usage patterns

The Auto Improve panel helps teams configure how Builder should use those signals for future improvement cycles.

Two operating modes may be available:

  • Review Mode: Builder prepares the next improvement cycle, then waits for confirmation.
  • Full Access: Builder can continue through approved improvement cycles without another manual confirmation step.

Auto Improve is plan-gated. Free workspaces can review setup, but enabling the workflow requires a paid Builder workspace.

In the hosted Builder experience, the main rail is organized around core surfaces:

  • Home: start a new app from a prompt or continue building from the main composer (Open Builder)
  • Projects: browse apps in the current workspace, sort them, and open app details (Open Projects)
  • AI Chat: continue work on an existing app with chat, preview, and approvals (Open AI Chat)
  • Templates: discover official or community starters and save your own apps as templates (Open Templates)
  • Library: store reusable prompts and theme prompts (Open Library)
  • Settings: review workspace limits, managed model access, workflow defaults, and integrations (Open Settings)

Inside an active app, the review panel can include:

  • Preview
  • Annotate
  • Code
  • Problems
  • Security
  • Configure
  • Cloud
  • Auto Improve
  • Publish

Typical Builder workflow​

  1. Launch Builder from OXVO and confirm the right workspace.
  2. Create a new project or import a GitHub repository.
  3. Describe what to build from Home or continue inside AI Chat.
  4. Review the result in Preview.
  5. Use Code, Problems, and Security to refine the app.
  6. Use visual editing when the change is copy- or UI-specific.
  7. Enable Builder Cloud if the app needs auth, database, storage, secrets, or backend operations.
  8. Connect OXVO and OXVO Sessions signals when you want richer support and product context.
  9. Use Auto Improve when Builder should prepare future improvement cycles from real usage and support signals.
  10. Publish, deploy, or connect GitHub when the app is ready to share.
  11. Save reusable work as a template, prompt, or theme prompt when the pattern should repeat.

When to use Builder Cloud​

Frontend-only apps can stay in the default Builder flow.

Enable Builder Cloud when the app needs:

  • authentication or user accounts
  • database tables and server-side data
  • file uploads or managed storage
  • secrets and environment-backed services
  • SQL tools
  • usage visibility
  • logs
  • backend operations

Builder Cloud gives the app managed resources, but teams should still review production requirements before treating a generated app as a fully governed production system.

Publishing expectations​

Builder supports a publishing and deployment workflow for moving an app from draft to a shareable or production-ready state.

Depending on your workspace and enabled integrations, publishing may include:

  • OXVO-hosted preview or app URLs
  • static-first publishing
  • supported custom domains on eligible paid workspaces and hosted deployments
  • GitHub connection and sync
  • deployment handoff through connected providers such as Vercel

Do not use publishing as a substitute for product review. Always verify Preview, Problems, Security, and Cloud state before sharing an app broadly.

Hosted Builder expectations​

This documentation focuses on the hosted OXVO Builder product.

In hosted Builder:

  • repository import is GitHub-first
  • workspace models are managed by OXVO administrators
  • personal model-provider API keys are not the normal hosted workflow
  • local desktop-only controls are intentionally hidden
  • preview refresh and restart behavior is handled automatically whenever possible