Inkloom ships the infrastructure and the honesty before shipping the AI

The central argument here is architectural, not aesthetic: general image models produce logo-shaped outputs, not logos. A bitmap that looks like a mark is not the same thing as a mark that holds at sixteen pixels and scales to the side of a building. Inkloom is building toward a pipeline of specialized models that treat logo construction as a sequence of explicit, defensible decisions — brand analysis into concrete constraints, typography with optical spacing and custom ligatures, symbol construction from geometric primitives with shared radii and tangent junctions, and composition using clear-space ratios derived from the mark's own geometry rather than arbitrary padding.

The intended output is a specification, not a raster image. That distinction matters practically: a specification can be handed to a printer, a sign maker, or a designer who needs to adapt it. A sampled bitmap cannot.

What's notable about this README is how much of it is about what doesn't exist yet. Generation is not live. Credits are reserved, not spendable. Feature flags that would enable generation default to off and are not togglable from the console — the repo explains this is deliberate, because enabling a flag for a nonexistent feature exposes a broken surface rather than a preview. What does run today is the platform infrastructure: accounts, authentication, a credit ledger, an access-code system, and an operations console with restore-tested backups and a deployment path that refuses to migrate a database whose identity hasn't been confirmed.

The repo is published for auditability, not distribution. The engineering choices are worth reading on their own terms. The test suite runs against a real database, a real browser, and a real mail server rather than mocks, because transaction guarantees cannot be tested with a mock. The concurrency test that gets called out specifically fires twenty-five simultaneous redemptions of a single access code at a live database and asserts that exactly one redemption, one ledger entry, and one balance result — a real test of a real invariant.

The stack is Cloudflare Workers, Postgres, and React Router, served from a single origin, which is what makes the session cookie first-party and eliminates cross-origin handling entirely.

For anyone building AI-adjacent products, the honesty about what's live versus what's coming is worth noting as a pattern. The product pages apparently say generation isn't live; the README says it plainly; the infrastructure enforces it. Whether the model architecture delivers on the construction-over-sampling premise is still an open question — the models themselves haven't shipped — but the framing of the problem is sharper than most logo-generation pitches.