DeplAI
— credits
DeplAI

Application

Dashboard

HomeYour ProfileOrganizationsUsageDocumentation

Services

UI/UX customizerSecurity AgentDASTCloudDeployInstance ManagementCode ReviewerSoonSessions

BYOK

KeysCatalogCompareUsage

Account

BillingInvoicesCreditsRefer & EarnNEWIntegrations
Settings
DE

DeplAI

Free

— creditsFree
deplaiDocumentation

Start here

Services

Account and models

Help and reference

Services

UI/UX customizer

**UI/UX customizer** restyles a project’s **frontend only**: design tokens, screens, responsive layout, accessibility, and visual assets. It does **not** rewrite APIs, authentication, database logic, or other backend business rules.

UI/UX customizer restyles a project’s frontend only: design tokens, screens, responsive layout, accessibility, and visual assets. It does not rewrite APIs, authentication, database logic, or other backend business rules.

If a proposed patch touches a protected business-logic file, Functional safety fails and the change is rejected.

Open Services → UI/UX customizer with a project selected.

---

What it can change

CapabilityExamples
Targeted screenSpecific routes and components you select
Design system upgradeColors, typography, spacing, component tokens
Responsive upgradeTablet and mobile layouts
Accessibility upgradeFocus order, contrast, skip links, ARIA labels
AssetsLogo, favicon, OG image, and other uploaded brand assets
Full UI/UX transformationBroad visual pass—still constrained by the business-logic boundary

---

What it cannot change

Protected areaWhy
API routes and handlersBackend contract stability
Auth and session logicSecurity boundary
Database models and migrationsData integrity
Server-side business rulesFunctional safety gate

Acceptance criteria include “No business logic changes.” Patches to protected paths fail validation.

---

Pipeline

Studio tabs

TabPurpose
PreviewLive preview (desktop / tablet / mobile)
ChangesFile-level change list
QualityAutomated quality checks
ManifestPlanned scope for the run
AssetsUploaded images and brand files
SettingsRun configuration

Bottom tabs

TabPurpose
DiffUnified diff view
LogsAgent and build output
CheckpointsSaved intermediate states
GitHubOpen PR when project is on GitHub
ReviewFinal approval before persist

---

Model and BYOK

Starting a run requires a ready model—the same Platform / BYOK / Auto picker as Security Agent.

ModeBehavior
PlatformDeplAI-hosted keys; consumes credits
BYOKYour key from BYOK → Keys
AutoBYOK if saved; otherwise platform

If blocked: *“Choose a platform model or a saved BYOK credential first.”*

For visual-heavy transformations, Best multimodal or flagship models with vision support work well. See BYOK models.

---

Step-by-step workflow

  1. 1Select the project and open UI/UX customizer.
  2. 2Describe the design goal in natural language.
  3. 3Pick a mode (targeted screen, design system, responsive, accessibility, or full transformation).
  4. 4Confirm the manifest (files and screens in scope).
  5. 5Inspect Changes / Diff, Preview, and Quality tabs.
  6. 6Complete Final review—last gate before changes persist.
  7. 7On GitHub projects, open a pull request from the GitHub tab.

The run appears under Sessions for history and logs.

---

GitHub integration

StepIntegration
SourceGitHub App–connected repository
OutputPull request after Final review (GitHub projects only)
ZIP projectsLocal diff export only—no PR

Same GitHub App model as Security Agent: login is identity only; writes use the App after your approval.

---

Troubleshooting

SymptomWhat to do
Functional safety failedPatch hit backend/business-logic file—narrow scope or pick frontend-only screens
Preview blankCheck build logs; confirm frontend framework detected
Model picker blockedAdd BYOK key or use allowed platform alias on your plan
No GitHub PR optionConnect GitHub project—not available for ZIP uploads
Quality checks failedReview contrast/accessibility report; adjust manifest

---

Best practices

  1. 1Start with Targeted screen before a Full UI/UX transformation.
  2. 2Run Security Agent separately—UI/UX customizer does not replace security scanning.
  3. 3Use Preview on all three breakpoints before Final review.
  4. 4Keep brand assets in Assets rather than hot-linking external URLs.

---

Related documentation

  • Security Agent — security scanning (separate workflow)
  • BYOK models
  • Sessions
  • Security and data

On this page

What it can changeWhat it cannot changePipelineStudio tabsBottom tabsModel and BYOKStep-by-step workflowGitHub integrationTroubleshootingBest practicesRelated documentation