Aperiodic Generator

The new discovery of a single shape that can't form patterns has not received the hype it deserves. Its unique properties are useful for improved aliasing in graphics, novel game design, encryption, wave propagation, and so much more. But they are difficult to work with, involving complex geometry which is entirely absent from AI training data. Before I built a generator, you would have to compute large iterations and crop out a small usable section from the whole, which looks similar to a Julia fractal in its raw form. Now, just specify a few parameters, and you have a highly-customizable patch of tiles in seconds.

Aperiodic Generator (site: https://aperiodicgenerator.com, API: https://api.aperiodicgenerator.com). It's a API-led workflow for producing large, gap-aware patches of non-repeating geometry inside a boundary you choose, with outputs aimed at real work: downloadable assets for 2D and 3D projects of all kinds.

Why care: This represents the frontier of geometry, which breaks known limits of aliasing in graphics, wave propagation (think noise-cancellation or heat dissipation), and many more unexplored fields. You get complexity without an obvious grid — especially useful for visual design, environments, fabrication patterns, and anything where pattern-detection is the judge.

What I shipped alongside the obvious ‘make geometry’ core: a Blender add-on because that’s where a lot of creators actually want the geometry to land — not in a one-off screenshot, but in a scene with materials, lighting, and iteration.

Pricing reality (indie-style): I’m trying to keep this honest for solo makers vs. folks shipping commercial work, so there is a free tier for JPG/PNG previews, then Solo and Commercial paths for the formats and usage that matter when it’s not a hobby anymore.

What I’m still figuring out:

• How far “generator-first” UX can go before power users demand even deeper knobs.

• Which communities actually pay for tooling vs. which ones want free inspiration.

• How to market math-y products without sounding like a textbook.

Question: if you’ve ever wanted “non-repeating structure” in a project, what blocked you — tools, uncertainty about correctness, export pain, performance, or simply not knowing what to search for?

Also: brutal feedback welcome on positioning. I’m intentionally leaning into Generator branding even though there’s an API underneath, because “API” often signals integration work before people understand the benefit.