product directory / Vol. 01 / 2026

A clear, living directory of 17 curious projects, forged by one builder.

A public map of the products I maintain: what each one does, where it lives, what changed, and what comes next.

Projects
17
Spotlight
4
Origin
MMXXIV
Directory
PUBLIC
§ 01 The Product

17 maintained products,
one precise public directory.

The four spotlight products are the public front door. The full catalog preserves the canonical product, source, changelog, and roadmap links without pretending the projects share one runtime or release boundary.

§ 02 The Package

One focused way
to collect feedback.

SaaS Maker publishes a small React widget for bugs, feature requests, screenshots, and page-specific feedback. It performs no implicit network request: the integrating product decides where submissions go.

PACKAGE NOTES
Package
@saas-maker/feedback
Runtime
React 19
Input
A required onSubmit callback
Feedback
Bug · feature request · general
Attachments
JPEG · PNG · GIF · WebP
Network
Consumer-owned · no default endpoint
Docs
npmjs.com/package/@saas-maker/feedback
END · FOLIO 01
feedback-widget.tsx
$ pnpm add @saas-maker/feedback

import { FeedbackWidget } from '@saas-maker/feedback'

export function App() {
  return <FeedbackWidget onSubmit={saveFeedback} />
}
§ 03 Field Notes

Frequently asked,
straight answers.

The boundary is intentionally small: a directory and one package.

01 What is SaaS Maker?

SaaS Maker is a public directory for Sarthak Agrawal’s maintained products and the home of the @saas-maker/feedback package. It links each product to its canonical site, repository, changelog, and roadmap without merging their identities or release boundaries.

02 What does the feedback package do?

The React package collects bugs, feature requests, general feedback, screenshots, and optional page-element context. It calls the product’s required onSubmit callback and contains no hosted endpoint, project key, storage, or inbox.

03 How current is the directory?

The directory is rebuilt from the same public metadata used to track each product. That keeps names, canonical sites, repositories, changelogs, and roadmaps aligned without exposing private operational data.

04 Why do products keep separate sites?

Each product has its own audience and release boundary. SaaS Maker is the map: it helps visitors discover the work, then sends them to the product’s canonical home.

05 Where are the package docs?

The npm page at npmjs.com/package/@saas-maker/feedback renders the package README with installation, callback, payload, Pinpoint, screenshot, compatibility, and privacy guidance. No separate documentation site is required.