Two ways in, one governed record

The improve platform does not impose a single way of working. Whether you prefer to stay entirely within your existing scientific tools or build automated pipelines from the command line, the improve platform offers a complete interface for both. Every interface connects to the same central governed repository - the same versioned artifacts, the same audit trail, the same lineage. The choice of interface changes nothing about what the improve platform captures or how it governs your work.

Full feature interface - work in the tools you already know

This interface is for the scientist who wants full access to the improve platform without learning a new platform. You work in VS Code studio or RStudio exactly as you always have. The improve platform versions every run, capturing every execution environment, recording every decision without requiring you to think about it.

improve studio brings the complete improve environment into Visual Studio Code. Browse your analysis graph, check in changes, trigger runs, and navigate lineage without leaving your editor. The full power of the improve platform - versioning, reproducibility, evidence capture, audit trail, Analysis Graph - is available from within the environment you already work in.

TreeExplorer is the equivalent integration for RStudio. Browse and interact with your improve analysis graphs, check in changes, and trigger runs directly from within RStudio. For scientists working in R, it is the most natural entry point into the improve platform.

The improve Workbench is the graphical desktop client for Windows. It provides a visual representation of the analysis flow with colour-coded execution status, built-in version control, and automatic extraction of key model parameters from run outputs.

All three interfaces are full-featured - every improve capability is available regardless of which graphical interface you use.

Programmatic access - build your own pipeline

This interface is for the scientist or engineer who wants direct, programmatic control over every interaction with the improve platform. The improve CLI and REST API expose the complete platform as a scriptable infrastructure layer. Every action that can be performed through a graphical interface can also be performed from the command line or via API call.

The improve CLI provides command-line access to all platform functions on Windows, Linux, and Mac. Push and pull resources, create analysis steps, check in local changes as governed runs, cache datasets across multiple checkouts, and submit runs to HPC environments - all from the command line.

The CLI is the primary integration point for automation tasks. The improve platform can be embedded into automated pipelines, CI/CD workflows, and HPC job submission scripts - runs triggered programmatically, outputs captured automatically, lineage preserved without any manual step. This is the capability that goes beyond what graphical interfaces offer: not just accessing improve, but scripting improve by scinteco as infrastructure that runs underneath your entire analytical work.

The REST API provides direct programmatic access to all improve platform functions. Any action available through the CLI or graphical interfaces is accessible via the API - enabling custom integrations with internal tools, JIRA, Confluence, and automated reporting pipelines. The CLI itself communicates with the platform through the REST API, so the two are fully equivalent in capability.

Every capability available through the graphical interfaces is also available through the CLI and API - and vice versa. Choosing the command line does not mean losing access to the Analysis Graph, the audit trail, or the governed environment. It means accessing all of it programmatically, on your own terms.

see improve in a live demo

Request a demo

Two ways in, one governed record

Full feature interface - work in the tools you already know

improve studio - the Visual Studio Code extension

TreeExplorer for RStudio

improve Workbench

Programmatic access - build your own pipeline

improve CLI

REST API

A note on parity