# Damn Labs: free developer tools from Pixelact Studio

URL: https://pixelactstudio.com/labs

> Damn Labs is Pixelact Studio's lab for free, open source developer tools. See what each tool does with your data, and how to get software like it built.

Damn Labs is Pixelact Studio's experimental software lab. It publishes free, open source developer tools: Commitscape shows what a developer built from a Git repository's history, Hexlode processes images in the browser, and EnvSift checks and converts `.env` files. Pixelact Studio builds each tool to the engineering standards it sets for client work and publishes the source on GitHub.

## What is Damn Labs?

Damn Labs is the experimental and R&D branch of Pixelact Studio. Its home is [damnlabs.com](https://damnlabs.com), where each tool has its own subdomain. A tool earns a place when it makes a recurring job easier, answers a technical question in working code, or teaches us something that changes how we build.

Each tool is described at the stage it has reached: EnvSift and Hexlode are live, and Commitscape is live but in early development, with a command line and website that work end to end.

## Why does Pixelact Studio run Damn Labs?

Damn Labs lets us test ideas on our own time and gives buyers working code to inspect before hiring us. Client code stays private, so the lab is where anyone can read our code, tests, and decisions.

Commitscape records its architecture decisions as numbered ADRs, and its CI runs Rust, TypeScript, and end-to-end Chromium tests with accessibility checks. Hexlode runs CodeQL and a weekly test that pushes 500 images of 12 megapixels through one template while checking memory. Our [engineering standards](https://pixelactstudio.com/about/engineering-standards) set the same practices for client projects.

## Why are these free developer tools privacy-first?

Because developers paste secrets, private images, and company code into tools like these. Each tool does the sensitive work on your device wherever it can.

**Where data goes in each Damn Labs tool**

| Tool | What it does | Where your data goes | License |
| --- | --- | --- | --- |
| [Commitscape](https://pixelactstudio.com/work/commitscape) | Counts what a developer built from Git history: merged pull requests, reviews, and lines that still run | The CLI reads history locally and asks before uploading a report encrypted with AES-256-GCM, whose key only the link holds. The Commitscape website reads repositories you open on its servers | MIT or Apache-2.0 |
| [Hexlode](https://pixelactstudio.com/work/hexlode) | Converts, compresses, resizes, crops, and strips metadata from images, alone or in batches | Images are processed on your device. Analytics events exclude image bytes, filenames, thumbnails, and metadata | Apache-2.0 |
| [EnvSift](https://pixelactstudio.com/work/envsift) | Compares, validates, merges, and converts `.env` files | Pasted values and local files are processed in the browser. Analytics events exclude keys, values, and filenames | Apache-2.0 |

To check this yourself, open the Network panel in your browser's developer tools while you use EnvSift or Hexlode.

## What does the same engineering look like in client work?

The same patterns fit products that handle files, secrets, or data customers would rather not hand over.

- **Processing on the client.** A product can convert, compress, or strip metadata from files in the browser with WebAssembly, as Hexlode does, so the original never reaches your servers. We build this into [product development](https://pixelactstudio.com/services/product-development) work.
- **Encrypted sharing.** A report can be encrypted before upload, with its key after the `#` in the link, which browsers never send to servers. Commitscape's CLI works this way, so its servers store data they cannot read.
- **Background jobs.** Commitscape's Builder takes jobs from a Postgres queue and uploads results to object storage, the same shape behind imports, exports, and scheduled syncs in [internal tools and data systems](https://pixelactstudio.com/services/internal-tools).
- **Configuration hygiene.** EnvSift compares `.env` files because a variable missing from one environment can break a deploy that worked locally. A [software audit](https://pixelactstudio.com/services/software-audits) checks how your product stores secrets and whether any [API keys are exposed](https://pixelactstudio.com/blog/exposed-api-keys).

Client work adds what a free tool does not have: a named lead, a written scope with milestones, and code, accounts, and a repository your company owns.

## How do I start a project with Pixelact Studio?

Fill in the short form on [Start a project](https://pixelactstudio.com/start-a-project). We reply to every project inquiry within one business day.

1. **Describe the project.** Say what you want built or fixed, pick a budget range, and tell us how you heard about us.
2. **Book a discovery call.** We reply with times for the call. The 45-minute call has no slides: we ask what prompted this now and what a good outcome looks like, then say whether we fit.
3. **Review the proposal live.** Within 48 hours of the call, we walk you through scope, exclusions, milestones, and two or three options live, then confirm everything in writing.

To test an idea first, a [pilot sprint](https://pixelactstudio.com/services/pilot-sprints) from $4,500 proves one thing at a fixed price, and a software audit from $2,500 reviews a product you already have.

## Frequently asked questions

### Are Damn Labs tools free to use?

Yes. Commitscape, Hexlode, and EnvSift are free to use and open source. Hexlode and EnvSift use the Apache License 2.0, and Commitscape is available under MIT or Apache-2.0. You can read the source and run each tool locally. Hexlode and Commitscape also publish Docker images, and their repositories explain how to self-host them.

### Is Damn Labs a separate company from Pixelact Studio?

No. Damn Labs is Pixelact Studio's experimental and R&D branch. Pixelact Studio is the commercial side, with written scope and delivery responsibility for client software. Damn Labs holds self-directed tools and prototypes where the question comes before any brief. The same people build both, and every Damn Labs tool links back to Pixelact Studio in its footer.

### Do Damn Labs tools send my data to Pixelact?

Hexlode and EnvSift do not. They process your images and `.env` files in the browser and send only filtered analytics events to PostHog, never file contents, keys, or filenames. Commitscape's CLI uploads a report only after you say yes, encrypted so its servers cannot read it, and `DO_NOT_TRACK=1` turns off its anonymous usage count. The Commitscape website reads the repositories you open there on its own servers.

### Can Pixelact build a tool like this for my company?

Yes. A tool like EnvSift or Hexlode is usually an internal tool or a product feature, and we build both, priced by milestone after a discovery call. If you are not sure the idea works, a pilot sprint from $4,500 proves one thing first at a fixed price, such as one automated workflow or a technical proof that browser-side processing handles your files.

### How do I report a bug or request a feature in a Damn Labs tool?

Open an issue on the tool's repository in the [Pixelact Studio GitHub organization](https://github.com/pixelactstudio). Commitscape, Hexlode, and EnvSift are public repositories with issues turned on. Include the browser or platform, the steps that reproduce the problem, and what you expected. Damn Labs tools are free, so fixes ship on the lab's schedule rather than under a support agreement.

### Who owns the code when Pixelact builds software for my company?

You do. Your company owns the code, accounts, and repository, and the final code and files transfer once the final invoice is paid. Handover is written so any engineer can pick the work up. Damn Labs tools stay ours and open source, and nothing from your project appears there or anywhere public without your permission.