VG-Sign — an e-signature SaaS, shipped solo

The problem

Most e-signature tools are priced for enterprises and built for them. A small firm that needs a handful of signed documents a month ends up paying for seats it never uses — or emailing PDFs back and forth and hoping nobody edits one in transit.

What it does

VG-Sign is a working product, not a prototype. Four plans are live on the pricing page — Free, Pro, Team and Enterprise — and what each tier may do is decided in one place rather than by permission checks scattered through the codebase.

• Team accounts — members, seats, enforced two-factor authentication and SSO, all driven by the plan rather than toggled by hand per customer.
• Signed PDFs — a completed document produces a certificate and an exportable audit trail, with full Cyrillic support in generated output.
• Metered usage — envelope quota is counted by a single locked round trip in the database, so a plan's monthly cap holds even when four different routes create envelopes at once.
• Admin controls — seats, Enterprise status and API allowance can be set by hand when a deal needs terms the self-serve tiers do not cover.

How it was built

Next.js App Router and TypeScript on the front, Supabase for data and auth, Stripe for billing, Resend for transactional mail, and pdf-lib with MuPDF for document generation. 165 of the repository's 1,052 files are tests — Playwright and Vitest cover the flows where a bug costs money: pricing, tiers and document generation.

The interesting constraint was scope, not technology. Every feature had to pay for itself in a product one person maintains.

What this demonstrates

For agencies weighing overflow capacity: this is the full stack of a commercial product — payments, multi-tenancy, authentication hardening, document generation and deployment — delivered and running, by one developer.

Related services: White-label development for agencies · Web apps