dcupl Console

The dcupl Console at console.dcupl.com is where a project's files live: models, data, the loader configuration and scripts. You run the project as an application in the browser, deploy workflows and REST API (RAPI) instances from it, and your own app loads the same files with the dcupl SDK. How the console fits next to the SDK and the CLI is on Architecture.

Where things are

The sidebar of a project:

• Applications runs an application or a quick run and opens it in the five views, among them the Data Explorer and the Quality Analyzer (Applications). Its Connect tab inspects your own running app (Debugging with Console), and Loader Configuration lists what dcupl.lc.json declares (Loader configuration).
• Workflows: workflow templates, deployments and runs (Workflows).
• REST APIs: API templates and deployed instances (REST APIs, MCP endpoint).
• dcupl Cloud → Version Manager: the project's file versions (see File versioning).
• Project Settings: General (name and Project ID), Members (see Roles), Sources, API Keys, Billing (owners only) and Reporting.

The file editor sits on the right-hand rail; its + menu opens Import Data and Create Model. Viewers see only Applications and Project Settings → General. Workflows and REST APIs are on for new projects; if either entry is missing, ask your dcupl contact to turn it on for your project.

Getting started

New to the console? Your first console project walks through it in five steps: create a project, import a CSV, check the inferred model, run the application and load it from your code.

Coming from the previous console? During the transition, Previous console in the account menu opens it at v1.console.dcupl.com.

By role

• You build an app on console data. Read Applications and Loader configuration, pick a key on API keys, then load the project from code: Load from the console and the Console + Loader setup.
• You manage the data. Importing data, Models in the Console, Sources and, for imports on a schedule, Workflows.
• You serve data to other systems or to agents. REST APIs, scripted endpoints and the MCP endpoint for AI agents, where it is turned on.
• You run the project. Members and roles below, API keys and Reporting.

Key concepts

Projects

A project holds models, data files, scripts, workflows, REST API templates and variables (named values for workflows; a new project starts with dcupl_version and dcupl_api_key). New projects are private: the CDN serves their files only to requests that carry one of the project's API keys. Browser apps use the seeded Browser (read-only) key.

File versioning

Project files live in named versions, managed under dcupl Cloud → Version Manager:

• draft: the version every project starts with and the console's default source. The SDK loads it unless you pass another version.
• Other versions (for example production): created by copying an existing version, served from the CDN the same way, and selectable as a source.

Roles

You sign in with email and password, or with Google or GitHub. What you can do in a project depends on your role in it; owners invite members under Project Settings → Members.