Epsilon

A structured canvas workspace for your ideas

Visit Website
June 5, 2026 Why I built Epsilon

Over the past few years I've tried dozens of note-taking and whiteboard tools. Some were great for documentation but felt restrictive. Others gave complete freedom but quickly became messy as projects grew.

Epsilon started as a side project to solve that problem for myself.

The idea was simple: create a canvas where notes, code snippets, images, todos, and markdown documents can live together without forcing users into a predefined structure.

After a month of building, testing, and collecting feedback, it has grown into a workspace that people are already using for planning projects, organizing research, and managing personal knowledge.

I'm still actively building and would love feedback from other builders.

1 Comment

  1. 1

    The risk with Epsilon is not the canvas idea. That part makes sense.

    The risk is that “notes, code snippets, images, todos, and markdown in one workspace” can make it sound like another flexible productivity tool, and that category is brutally crowded.

    I’d probably sharpen it around the first use case where structure actually breaks: planning messy technical projects, organizing research with code/context, or turning scattered build notes into something usable.

    The product will be easier to sell if people understand the painful moment first, not the list of things the canvas can hold.

About

I built Epsilon because I was frustrated by tools that were either too rigid or too chaotic. Epsilon gives people a flexible canvas to organize notes, code, tasks, and ideas in a way that fits their workflow.