Our products solve different problems, but the same team writes them with the same habits: typed code, tests before a release, and a confirmation before anything that cannot be undone.
About
A small team that builds and ships its own products.
Sunsato builds software in Antalya, Türkiye. We make our own products, deliver web projects for clients through The Piron, and publish free tools at Sunsato Labs.
The ecosystem thesis
Why an ecosystem
That is why ADE, Tideline, Vulcanus, and Sunsato BI Studio are written under the same rules despite looking at very different problems. One is decision intelligence, one is a system tool, one is a command-line product, one is a report design tool — yet all four treat the deterministic core, the honest status report, and reversibility the same way.
The Piron is the client-facing side of that same floor. Delivered projects show the structure works in practice, not only in theory.
Relationship types
Structure
The relationships under Sunsato are of different kinds; they are not flattened into one list.
Method
How a product gets built
The same order runs on every product: prove the core value first, grow the architecture after.
A working core first
For ADE the order was data → clustering → fuzzy score → recommendation → report. For Tideline it was app list → leftover scan → review → move to Trash. Heavy architecture is not built for an unvalidated idea.
Real-world output
The measure is a working, demonstrable result. A feature counts as finished only when it holds up against real data.
Identity apart from implementation
What a product is gets defined independently of how it is written. Module boundaries follow the work, and abstraction never becomes more complex than the problem it solves.
Simple flow, strict validation
The user-facing side stays simple; the system side is never loosened. Input validation and state checks are the tightest part of the product.
Risky operations logged and guarded
If an operation matters, it is logged. Where files are deleted or hardware is involved, safety beats speed — Tideline preferring the Trash over permanent deletion is that rule in practice.
Research tied to an outcome
Research happens, particularly around ADE, but it connects to a usable result. Producing an academic archive is not the goal.
Able to stand alone
Each product is built to still make sense if it were pulled out of the ecosystem. The dependency is a consequence, not a design choice.