Priced by what you're building

Pre-rendered pages served from a CDN. No server, no database, nothing to patch. Fast, cheap to run, and easy for your team to keep editing.

• Design system matched to your brand (or built from scratch)
• Responsive, accessible pages — semantic markup, keyboard nav, AA contrast
• SEO baseline: metadata, Open Graph, sitemap, robots, structured data
• Editable content in structured files, or a headless CMS if you prefer
• CDN hosting, custom domain, automatic HTTPS
• Deploy pipeline: preview on every push, publish on merge, one-click rollback
• Repo, hosting, and domain set up in your name + a handover walkthrough

• The site is mostly content — pages, posts, docs — not an application
• You want it to load instantly and cost cents to host
• Non-developers should be able to make copy changes

This site and the marketing pages of most small businesses are built this way.

A real application: student accounts, a course catalogue, video lessons with access gating, quizzes, progress tracking, payments, and an admin area to author it all.

• Auth: signup / login, sessions, password reset, role-based access (student / staff / admin)
• Course model: categories, courses, sections, lessons, quizzes — all admin-editable
• Video delivery (Vimeo / YouTube / self-host) with enrolment-gated access + free previews
• Quizzes with scoring and quiz-gating between lessons
• Progress tracking + certificate generation on completion
• Payments: one-off course purchase and/or subscription pass (Razorpay / Stripe / Cashfree)
• Cart + checkout, coupons, and a post-purchase dashboard
• Database, migrations, backups, and a containerised deploy (Cloud Run / ECS)
• Admin CRUD for every content type + a blog

• You're selling structured learning, not just hosting a few videos
• You need enrolment, payments, and completion tracking to actually work
• You want to own the platform rather than pay per-seat to a hosted LMS forever

courses.tech-zenigmatica is an LMS built exactly this way — the full spec and cost model are the reference for this option.

Anything with its own logic, data, and users that isn't a website or an LMS — a customer portal, an internal tool, an admin dashboard, the first version of a SaaS product.

• Data model and API design for your domain
• Auth + authorization (roles, teams, per-record permissions as needed)
• The core screens: list / detail / create / edit, plus the dashboards that matter
• Integrations with the third-party services you already use (via their APIs)
• Background jobs, scheduled tasks, webhooks where the workflow needs them
• Database, migrations, backups, secrets management
• Containerised deploy with CI/CD, preview environments, and monitoring
• An architecture doc and a cost model for running it

• Off-the-shelf tools don't fit the workflow and spreadsheets have stopped scaling
• You have a clear first use case — one job it must do well — not a wishlist
• You'd rather ship a tight MVP and iterate than spec everything up front

Support-triage tools, client portals, and internal ops dashboards are typical.