Client projectCustom softwareMedia, arts and publishing
A digital-publishing startup.
A digital-publishing startup had a broad statement of work for a secure manga and magazine reader with paid entitlements and offline reading, and needed an executable architecture, an estimate and a discovery plan before committing to a build. Separately, its existing demo product was down after a move from AWS to GCP.
Discovery and architectureWeb app
Reader and publisher user journeys, with responsive reader modes
HTML5/PWA and offline approach
Wallet and email authentication
An entitlement model covering ERC-1155 and ERC-721 token purchases on Base or Polygon, and card purchases through Stripe
A secure content pipeline: S3 storage with KMS encryption, CloudFront delivery through signed URLs, and watermarking
Publisher CMS scope, analytics, and a system architecture specifying Next.js 14, NestJS, PostgreSQL with Prisma, and Redis with BullMQ
Non-functional requirements, team composition as a managed pod, QA and security strategy, acceptance criteria and a risk list
Discovery outputs and delivery planning
Deployment troubleshooting on the startup's existing demo environment after its move from AWS to GCP: an SSL failure, then a deployment sitting in the wrong GCP project, and a codebase review with content-moderation requirements
The startup had an architecture to decide against rather than a guess, and its existing product came back to health after the deployment was found in the wrong GCP project.
Done again today
Done again today, work like this usually costs $2.5K to $5K (Two-week prototype). The free plan says whether it fits before anything is priced.
A working version in 2 weeks, on real data and clickable. The repository is yours.
$2.5K to $5K, usually fixed-price
2 weeks
Your project, next
Say so in a few sentences. The free plan comes from the person who built this one.