dxStudio
Where an integration is written, run and debugged. Each one is a single script you can read top to bottom. Write it yourself or with an AI assistant — every script is checked before anything is published.
dxCompany is operational infrastructure for the work between your systems. Integrations become readable scripts. They run on your machines, on schedule, and every run leaves a record. Your data stays where it is.
Most teams pay for one product to extract data, another to transform it, another to schedule it, another to move files, and one more to watch the rest. None of them share a sign-in or a run history. dxCompany brings all of that into one place, with one sign-in and one record of everything that ran.
Most companies run on integrations nobody can see. They work until the person who wrote them is on vacation.
Start with a single program on one computer. Grow to a fleet of agents your IT team manages. The script does not change.
Where an integration is written, run and debugged. Each one is a single script you can read top to bottom. Write it yourself or with an AI assistant — every script is checked before anything is published.
Runs published scripts on a schedule, on a machine inside your network. A new version goes live only when a person there makes it active.
One view of every agent and every run. Manage people, connect new machines and send versions to them. Hosted by us or installed on your own servers.
Not every job needs a fleet. Publish a single script as one program with its own run window, schedule it with Windows Task Scheduler, and hand it to a client through your account's Downloads page.
Describe the work as a script in dxStudio. Run it, step through it, and see exactly what it would send before it sends anything.
One click publishes a numbered version to your Console. Send it to the agents that should have it. Nothing goes live by itself.
The agent runs it on schedule and reports back. Open any run to see its steps, its log and everything it handled.
The same scripts, started by more than a clock — and a governed history of the data they move.
| Capability | What it does | Status |
|---|---|---|
| Endpoint triggers | Start a script from an inbound HTTP request; the agent owns the listener | Coming next |
| SFTP triggers | Start a script when a file arrives | Coming next |
| dxLake | History, point-in-time queries and audit over your existing relational databases | Coming next |
| dxInsight | Derived data with declared inputs and outputs, rebuilt when its sources change | Fast follow |
| dxDashboards | Operational visibility for the people who run the business: what ran, what moved, what needs attention | Fast follow |
We are onboarding a small first group of companies. Leave an address and we will write once, when there is a place for you.