Public software · Maintained by Fabreco Studio

Tools and open-source work

Each project begins with a narrow, real problem. This directory explains not only what the software does, but also how it behaves, what it does not promise, and how to use it responsibly.

Browser tools

Ready-to-use utilities with local-first interfaces and explicit privacy behavior.

01Browser tool · Design utility

Image to White

A focused browser utility for preparing white logos and artwork for dark interfaces, slides, video, print layouts, and sponsor walls.

Input
PNG, JPG, JPEG, WebP, SVG
Output
Transparent PNG
Read examples and limitations
02Browser tool · Developer utility

Form data to JSON

A local-first developer tool that turns raw form bodies and URL query parameters into structured, readable JSON without requiring an account.

Accepts
Form body, query, or full URL
Repeated keys
Preserved as arrays
Read examples and limitations

Open-source resources

Source repositories for maintainers, developers, and teams solving a specific engineering task.

03Open source · Curated reference

Organization README collection

A maintained reference for teams that want their GitHub organization landing page to explain purpose, projects, contribution paths, and identity clearly.

Format
Curated Markdown collection
Audience
Maintainers and engineering teams
Read examples and limitations
04Open source · Database migration

SQLite to Turso

A focused Node.js migration script for a specific operational need: copy local SQLite data into a cloud-hosted Turso database with a traceable run.

Runtime
Node.js
Source
Local SQLite
Read examples and limitations

Fabreco tool standard

What every Fabreco tool should make clear

A small utility still deserves the basics of maintained software. These are the checks used across the collection.

  1. 01

    A defined job

    The tool names the problem it solves instead of presenting itself as a universal platform.

  2. 02

    Visible limits

    Known edge cases, output constraints, and risky assumptions are documented near the use cases.

  3. 03

    Understandable data handling

    Users can tell whether input stays in the browser, reaches an API, or goes to an external provider.

  4. 04

    A maintenance path

    Source, ownership, contact details, and relevant documentation are available for continued review.

Created and maintained by Fabreco Studio
Editorial content reviewed July 2026

EngineeringGitHub