Skip to content
Desifexdocs
WebsiteSign in
Introduction

Start here

  • What Desifex is
  • Your first application
  • The workbench
  • What to expect

Building

  • Describing what you need
  • Watching a build
  • Changing your mind
  • When a build fails
  • Showing it a file
  • Choosing a design system
  • Asking for settings
  • When it asks you
  • Starting from what you have

Shipping

  • Versions
  • Environments
  • Deploying
  • Going back

Running it

  • Addresses and domains
  • Who can reach it
  • People who sign in
  • Published files
  • Integrations
  • Appearance
  • Redirects and search engines
  • Configuration values
  • Your data
  • Visitors

Your workspace

  • People and roles
  • More than one workspace
  • Organising applications
  • Your own design systems
  • Your profile
  • Where records live

For developers

  • What gets built
  • Taking one over

Reference

  • Glossary
  • Limits
  • Troubleshooting

For developers

What is actually generated, and what to do when you inherit one.

Two pages, for the technical colleague rather than the person who commissioned the application.

What gets built is the stack, the shape of the repository, and — more interestingly — the parts the platform provides so the application does not have to. Taking one over is for the developer who has just been handed one of these and wants to know what they are looking at.

  • What gets builtThe stack, the shape of the repository, and the parts the platform provides rather than the application.
  • Taking one overFor the developer who has just been handed an application built here.
PreviousWhere records liveNextWhat gets built

© 2026 Desifex

WebsiteSecurity Request access Sign in