A public map of the products I maintain: what each one does, where it lives, what changed, and what comes next.
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.
The concise product story: CodeVetter, Post-train LLM, HeyPace, and HiSignal. SaaS Maker is the directory for everything around them.
Every maintained product in the public directory, with its canonical product or source URL, changelog, and roadmap.
AI code review platform — desktop-first, works offline.
View repository →A local factory for training, evaluating, and running specialist language models.
View repository →Local-only macOS voice agent that can understand what is on your screen.
View repository →Evidence-backed daily intelligence across technology, startups, finance, and public markets.
View repository →SaaS Maker publishes a small React widget for bugs, feature requests, screenshots, and page-specific feedback. Product operations stay in their own repositories; the feedback inbox does one job.
$ pnpm add @saas-maker/feedback
import { FeedbackWidget } from '@saas-maker/feedback'
export function App() {
return <FeedbackWidget projectId="pk_your_project_key" />
} The feedback package is the one reusable SaaS Maker runtime. Install it, connect a project key, and keep product feedback in one focused inbox.
The boundary is intentionally small: directory, package docs, and feedback.
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.
The React package collects bugs, feature requests, general feedback, screenshots, and optional page-element context. Each installation uses a public project key, while submissions are reviewed in the private feedback inbox at app.sassmaker.com.
No. Internal automation, marketing pipelines, schedules, skills, and host operations live in the separate private Fleet Workspace. SaaS Maker receives only an allowlisted public product projection for the directory.
No. CodeVetter and App Health are independent products with their own repositories, interfaces, and release boundaries. SaaS Maker may link to them in the directory, but it does not contain or operate their runtimes.
The Blume documentation site at saas-maker-packages.pages.dev covers installation, project keys, widget options, the feedback API, and submission handling. It is the canonical technical reference for the published feedback package.