Terms of use

The terms for using KPD Studio and its beta: what it is for, what you may put in it, and what may be removed. By signing in to the beta you agree to them.

Last updated 2 November 2026. KPD Studio is made by Chris Judd (“we”, “us”). These terms sit alongside the disclaimers on About, author and disclaimers.

What KPD Studio is for

KPD Studio is a tool for designing data pipelines: drawing them, describing them, and producing the pictures, documents and Terraform that go with a design. The beta is a preview, offered so testers can try it and tell us what works. It is not a production service.

Not for client work during the closed betaWhile KPD Studio is in closed beta, don’t use it for client or paid work, or for designs your employer or a client will rely on. Use it to try KPD Studio out, with made-up designs or the sample projects.

What you may put in it

Use KPD Studio for design work only. A project holds only KPD Studio’s own files:

the project file, pipelines (.kpd) and storyboards (.kpdstory);
schemas (Avro .avsc, Protobuf .proto and JSON Schema .json);
what KPD Studio exports: pictures, design documents, technical exports and Terraform;
Markdown notes next to the project, such as a gap report.

Anything else is refused when saved and left out when a project is imported, and each file must really be what its name says. The beta also limits the size of an imported project and of each file. A project is not a place to store, back up or share other files.

Everyone in the beta can see every project

Beta projects are kept in one shared repository: every tester can open, change and export every project. So don’t put in anything you wouldn’t show the other testers:

no confidential client or employer material: use made-up names, or the sample projects;
no personal data about real people;
no passwords, API keys or other credentials (KPD Studio refuses them where it can).

Respect other testers’ work: don’t delete or spoil projects that aren’t yours.

Acceptable use

Don’t use KPD Studio or the beta to:

store, share or link to anything unlawful, harmful, or that you don’t have the right to use;
try to get round its limits, its security or its sign-in, or reach anything other than your own session;
put an unreasonable load on the server, for example by scripting or scraping it;
let anyone else use your sign-in.

If you find a security problem, tell us rather than testing it further: see Send feedback.

What we may remove

We may remove, without notice, any file or project that isn’t design work for KPD Studio or that breaks these terms, and we may suspend or end access for anyone who breaks them. We may also tidy up the shared repository at the end of a beta round, and change or stop the beta at any time.

Your work and your copies

Your designs are yours. Putting a design in the beta doesn’t give us rights in it, beyond keeping it so the beta works, backing it up, and looking at it when we need to run or fix the beta.

The beta is backed up every night, but it is a preview and work can be lost. Keep your own copy of anything that matters with Export project (.zip).

Feedback and how the beta is used

If you send feedback, we may use it to improve KPD Studio without owing you anything for it. The beta records who signs in and how the designer is used (for example which palettes are used and when errors happen), to run the beta and improve KPD Studio. It never sends your designs anywhere else.

No warranty

KPD Studio and the beta are provided as they are, without any warranty, and we are not liable for any loss arising from their use, including from using what KPD Studio generates. The full disclaimers are on About, author and disclaimers. Nothing in these terms limits liability that the law doesn’t allow to be limited.

Changes and contact

We may update these terms; the date at the top says when they last changed, and using the beta after a change means you accept it. These terms are governed by the law of England and Wales. Questions to cpljudd@hotmail.com.