Documentation Index
Fetch the complete documentation index at: https://www.qovery.com/docs/llms.txt
Use this file to discover all available pages before exploring further.
Overview
Make the RDE Portal your own with custom branding, a tailored welcome screen, and per-blueprint layout configuration. These settings let you align the portal with your company identity and control the development experience your builders get.Branding
Navigate to Admin > Settings to configure portal-wide branding.| Setting | Description |
|---|---|
| Portal Name | Displayed in the header and browser tab title. Use your company name or a team-specific label. |
| Logo (Light) | Your company logo for light mode, shown in the top navigation bar. Upload a PNG or SVG file. |
| Logo (Dark) | Your company logo for dark mode. If not provided, the light logo is used in both modes. Upload a PNG or SVG file. |
| Accent Color | The portal generates a full color palette from your accent color - buttons, links, accents, and hover states all adapt automatically. Use the color picker or enter a hex value. |
Branding changes take effect immediately for all users. No restart or redeployment is required. The portal automatically applies the appropriate logo variant based on the user’s system theme (light or dark mode).
Welcome Screen
Configure the welcome screen that builders see when they first log in or when they have no active workspaces. Navigate to Admin > Settings > Welcome Screen.| Setting | Description |
|---|---|
| Title | The headline on the welcome screen (e.g., “Welcome to Acme Dev Portal”). |
| Description | A short paragraph explaining what the portal is and how to get started. |
| CTA Button Text | The label on the call-to-action button (e.g., “Create Your First Workspace”). |
Layout Configuration
Each blueprint can have its own layout settings that control what builders see inside the workspace editor. Navigate to Admin > Blueprints > [Blueprint] > Settings > Layout.Tabs
Choose which tabs appear in the workspace editor. Available tab types:- Chat - The OpenCode chat panel for AI-assisted development
- Claude Code - Terminal tab with Claude Code pre-configured
- Terminal - A standard terminal session in the workspace container
- Custom command tabs - Tabs that run a specific command when opened
Custom Tabs
Define custom tabs that execute a specific command in the workspace container when the tab is opened. This is useful for common development tasks. Examples:- A tab named “Dev Server” that runs
npm run dev - A tab named “Django Server” that runs
python manage.py runserver - A tab named “Tests” that runs
npm test -- --watch
Lock Layout
Enable Lock Layout to prevent builders from adding or removing tabs in the workspace editor. When locked, builders see exactly the tabs you configured - no more, no less. Use this when you want a consistent, controlled experience across all workspaces using this blueprint.Preview Panel
Toggle the preview panel visibility for the blueprint. When enabled, builders see a live preview of their running application directly in the workspace editor with viewport switching for desktop, tablet, and mobile. Disable the preview panel for blueprints where a live preview is not relevant (e.g., backend API services, CLI tools, data processing scripts).AI Configuration
Configure AI providers for each blueprint in a single, unified settings panel. Navigate to Admin > Blueprints > [Blueprint] > Settings > AI Configuration. The AI configuration uses an accordion interface where each provider can be independently enabled and configured.Anthropic (Claude)
Controls both Claude Code (terminal) and can power the Chat panel.| Setting | Description |
|---|---|
| Enabled | Toggle to enable or disable Anthropic as a provider for this blueprint. |
| Authentication Mode | Choose between User OAuth (builders authenticate with their own Anthropic account) or API Key (you provide a key, billed to your organization). |
| API Key | Required when using API Key authentication mode. Stored encrypted with AES-256-GCM. |
| Model | The Claude model to use (e.g., claude-sonnet-4-20250514). |
OpenAI
Powers the Chat panel with OpenAI models.| Setting | Description |
|---|---|
| Enabled | Toggle to enable or disable OpenAI as a provider. |
| API Key | Your OpenAI API key. Stored encrypted with AES-256-GCM. |
| Model | The model to use (e.g., gpt-4o). |
Custom Provider
Use any OpenAI-compatible API endpoint as the Chat panel provider.| Setting | Description |
|---|---|
| Enabled | Toggle to enable or disable the custom provider. |
| API Key | API key for the custom endpoint. Stored encrypted with AES-256-GCM. |
| Model | The model identifier expected by the custom endpoint. |
| Endpoint URL | The base URL of the OpenAI-compatible API (e.g., https://your-llm-gateway.internal/v1). |
You can enable multiple providers simultaneously. Anthropic powers Claude Code, while the Chat panel uses whichever provider is configured for it (Anthropic, OpenAI, or Custom). If multiple chat providers are enabled, the first enabled provider in order (Anthropic, OpenAI, Custom) is used.
Next Steps
Blueprint Management
Register and configure blueprint templates.
Access Control
Control who can access each blueprint.
Member Management
Invite and manage team members.