# Pixelact Studio work you can open, run, and read

URL: https://pixelactstudio.com/work

> Pixelact Studio work, labeled honestly: open source tools we built that you can run and read today. No client case studies yet, and we won't invent any.

Every item carries one label: Client Work, Studio Demonstration, or Open Source. Today every item is Open Source, so you can try the tools and read the code before you talk to us.

Pixelact Studio work today is open source software we built ourselves, not client case studies. [Commitscape](https://pixelactstudio.com/work/commitscape), [Hexlode](https://pixelactstudio.com/work/hexlode), and [EnvSift](https://pixelactstudio.com/work/envsift) are free developer tools from [Damn Labs](https://pixelactstudio.com/labs), our experimental and R&D branch, and [VidcastX](https://pixelactstudio.com/work/vidcastx) is self-hostable video infrastructure still in development. Each page states its label, status, stack, and the decisions behind it. Client Work will appear here only when a client gives written permission to show it.

## Pages in this section

- [Commitscape: open source git history analysis tool](https://pixelactstudio.com/work/commitscape): Commitscape is an open source tool from Damn Labs at Pixelact Studio that shows what developers built, from git history and GitHub. How it works and why.
- [Hexlode: open source batch image editing in the browser](https://pixelactstudio.com/work/hexlode): Hexlode is open source batch image editing in the browser, built by Pixelact Studio's Damn Labs. How its engine, codecs, privacy model, and tests work.
- [EnvSift: open source .env file tools in the browser](https://pixelactstudio.com/work/envsift): EnvSift is an open source app by Damn Labs at Pixelact Studio that compares, validates, and converts .env files in your browser. See how it was built.
- [VidcastX: open source, self-hostable video infrastructure](https://pixelactstudio.com/work/vidcastx): VidcastX is open source, self-hostable video infrastructure by Pixelact Studio. See what works today, how its FFmpeg to HLS pipeline runs, and what V1 adds.

## Frequently asked questions

### Why doesn't Pixelact Studio show client case studies?

Pixelact Studio has no published client case studies yet, and we won't invent any. Client code, data, and names stay private unless the client agrees in writing. Until the first case studies are approved, the proof is software anyone can inspect: try Commitscape, Hexlode, and EnvSift, read the source on GitHub, and see how each one is tested and why it was built the way it was.

### What do the Client Work, Studio Demonstration, and Open Source labels mean?

**Client Work** is paid work a client has allowed us to show. **Studio Demonstration** is a finished, working product we built ourselves to show how we build. **Open Source** is a tool or library we built and released for developers, with its source public. Each item carries exactly one label, and a studio demonstration never carries invented users, revenue, or metrics.

### How can I judge your work if none of it is client work?

Judge the engineering directly. The public repositories show how we structure code, test it, and record decisions, and our [engineering standards](https://pixelactstudio.com/about/engineering-standards) apply the same practices to client projects. For a low-risk first step on your own product, a fixed-fee [software audit](https://pixelactstudio.com/services/software-audits) or a [pilot sprint](https://pixelactstudio.com/services/pilot-sprints) shows how we work before you commit to a larger build.