Logo design as construction, not sampling
General image models produce logo-shaped pictures with nothing behind them; Inkloom is building a pipeline that constructs a mark as a sequence of explainable decisions — and says plainly that the generator is not live yet.

What it does
Inkloom is a planned pipeline of specialised models for logo design. A brand-analysis model turns a business description — sector, audience, tone, competitors — into concrete constraints (stroke weight, width, geometry, counter shape, which symbol families fit); typography and symbol models then build the wordmark and mark under construction rules like shared radii and tangent junctions; a composition engine produces lockups and clear-space ratios taken from the mark’s own geometry. The goal is a mark that holds at sixteen pixels and on the side of a building, delivered as a specification you can hand to a printer — not a bitmap. What actually runs today is the platform underneath: accounts, a credit ledger, access codes and an operations console, with exports, brand kits, revision history and paid plans queued behind generation itself.
The interesting bit
The unusual move is what the README refuses to claim: generation is not live, credits are reserved rather than spendable, and the flags that would enable generation default to off and cannot be toggled from the console — a flag for a feature that does not exist is, in their words, “a broken surface rather than a feature.” The source is published so the security and data-handling claims can be audited, and the test suite runs against a real database, browser and mail server because a mock cannot hold a transaction guarantee.
Key highlights
- Four-stage construction: brand analysis produces constraints; typography handles optical spacing, display-size kerning and custom ligatures; symbols are composed from geometric primitives; composition handles optical alignment and lockup variants.
- The output is meant to be a specification — describable, defensible, reproducible — not a bitmap.
- Built on Cloudflare Workers, Postgres and React Router, with app and API served from one origin, which keeps the session cookie first-party.
- The test that matters most fires twenty-five simultaneous redemptions of a single access code at a real database and asserts exactly one redemption, one ledger entry and one balance survive.
- Operational discipline is visible: restore-tested backups, an alerting pair where each half watches what the other cannot see, and a deployment path that refuses to migrate a database whose identity has not been confirmed.
Caveats
- Generation is not live — the models are the pitch, the platform is the product; early access reserves credits you cannot yet spend.
LICENCEis all rights reserved and the repo is explicitly “not a distribution”: you can read the engineering, not reuse it.- Operational documentation (deployment, runbooks, incident response) is kept internal, so this will not teach you to run the service.
Verdict
Worth a read if you care about how a generative-design product is staged — the spec-not-bitmap thesis and the audit-first engineering are the interesting parts. Skip it if you need a logo this afternoon or code you can borrow: the first is not live and the second is not licensed.
Frequently asked
- What is Inkloom-art/inkloom?
- General image models produce logo-shaped pictures with nothing behind them; Inkloom is building a pipeline that constructs a mark as a sequence of explainable decisions — and says plainly that the generator is not live yet.
- Is inkloom open source?
- Yes — Inkloom-art/inkloom is an open-source project tracked on heatdrop.
- What language is inkloom written in?
- Inkloom-art/inkloom is primarily written in TypeScript.
- How popular is inkloom?
- Inkloom-art/inkloom has 3.2k stars on GitHub.
- Where can I find inkloom?
- Inkloom-art/inkloom is on GitHub at https://github.com/Inkloom-art/inkloom.