iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Maniesta is Usman Murtaza’s account of building a dozen related web products as a solo developer—not a single app or a shared-code platform. His approach was to keep deployments and runtimes independent while applying common design conventions. The resulting portfolio spans education, productivity, consumer, business, and AI tools, with a mixed stack that includes React, Next.js, JavaScript, TypeScript, Node.js, and several data services.
Murtaza’s DEV Community article, published September 26, 2026, is a first-person account. It documents his choices and lessons, but does not independently verify usage, reliability, commercial performance, or the current availability of the products. Read Murtaza’s article on DEV Community.
What is Maniesta?
Maniesta is the name Murtaza gives to an ecosystem of 12 products he says he built. Rather than describing them as one application, he groups them into three broad areas: education and productivity, creative and consumer products, and business and AI. Their common identity comes from branding and design conventions, not a shared runtime or a single deployment.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →Education and productivity
- Maniesta Campus: role-based campus management.
- Maniesta School ERP: a multi-portal school dashboard for attendance, fees, and notices.
- Maniesta Notes: notes with authentication, tags, archiving, and real-time functionality.
- Maniesta Suite: GPA and CGPA tools alongside a scientific calculator.
Creative and consumer products
- Maniesta Play: music discovery and listening.
- Maniesta Weather: a weather dashboard.
- Maniesta Label: a fashion e-commerce storefront.
- Maniesta Veyra: clothing e-commerce with a custom print studio.
Business and AI
- Maniesta ResumeAI: an AI resume builder with ATS optimisation.
- ResumeAI Pro: a standalone resume-builder SaaS product.
- Maniesta AI Travel Planner: an itinerary generator powered by Gemini.
- Maniesta Digital: an agency website.
Murtaza describes the products as live and used, but his article provides no user counts or independent confirmation of either claim. A destination listed in the article shows that he presented a link, not that the product is currently accessible.
#1 Best Overall
How the architecture keeps the products separate
Murtaza’s model is “shared conventions, separate deployments.” In his account, the products share a design language, but each has its own deployment and technology choices. He explicitly says he did not use a monorepo or shared runtime. The products may link to one another, but do not share sessions or data.
The main benefit he identifies is isolation: a failure in one product should not take down the others. That independence also means repeating work, including authentication setup, deployment configuration, and design tokens. His article therefore describes a trade-off, not a universal prescription for multi-product development.
Rank #2
- HTML CSS Design and Build Web Sites
- Comes with secure packaging
- It can be a gift option
The stack varies by product
The title names React, Node.js, and TypeScript, but Murtaza does not say that all 12 products use those technologies. His article describes a mixed stack shaped by product needs and project age:
| Area | Reported choices |
|---|---|
| Frontend frameworks and languages | React for interactive apps such as Campus, ResumeAI, and School ERP; Next.js for Veyra and the AI Travel Planner, where server-side rendering and SEO mattered; Vanilla JavaScript for lighter tools such as Notes, Weather, and Play. Newer projects use TypeScript, while earlier ones use JavaScript. |
| Styling | Tailwind CSS on most newer work; styled-components on older React apps; plain CSS on utility tools. |
| Backend and data | Node.js and Express for custom APIs; Firebase for authentication, databases, and real-time features; PostgreSQL with Prisma for relational data; MongoDB where the schema was changing quickly. |
| AI integrations | OpenAI API for ResumeAI Pro and Gemini AI for the Travel Planner. Murtaza says both are accessed through server-side proxies rather than exposed to the client. |
| Deployment | Netlify. Murtaza reported that all 12 sites were on its free tier; this is his time-specific account, not a statement of current Netlify pricing or plan eligibility. |
The variation matters: describing Maniesta as a TypeScript ecosystem would overstate what the account establishes. Murtaza says TypeScript appears in newer projects, alongside JavaScript projects and tools built with different frontend approaches.
Rank #3
What solo development cost—and what Murtaza would change
Murtaza says a solo builder ends up handling product management, design, QA, DevOps, and customer support in addition to coding. He also acknowledges that some projects lack READMEs and that most lack tests. He presents those omissions as the cost of prioritising features and shipping, not as a recommended practice.
His article names several mistakes and lessons:
- Starting too many products at once: Murtaza says he pursued too many ideas in parallel. His advice is to ship a first product before investing heavily in a brand.
- Skipping documentation: some projects lack READMEs, which makes the work harder to understand and maintain.
- Leaving design conventions unversioned: he says he did not version the design system early enough.
- Assuming users would find the products: Murtaza says he underestimated active distribution. His line that shipping is “10% of the work” and distribution the “other 90%” is a rhetorical estimate from his essay, not a measured result.
- Choosing tools to fit the product: his mix of frameworks and services reflects a preference for matching technology to the task rather than forcing all products onto one stack.
He summarises one lesson as: “The lesson: patterns scale better than packages.” That is Murtaza’s opinion based on his experience, not a finding from a comparative study. In context, it means that consistent conventions can help related products feel coherent without requiring a shared software package or runtime.
Rank #4
- Brand: Wiley
- Set of 2 Volumes
- A handy two-book set that uniquely combines related technologies Highly visual format and accessible language makes these books highly effective learning tools Perfect for beginning web designers and front-end developers
When this approach may—and may not—fit
For a developer considering a family of small products, the useful question is not simply whether to use a monorepo. Murtaza’s account points to several practical trade-offs to weigh:
- Failure isolation: separate deployments reduce direct coupling, but do not guarantee that each product is reliable.
- Repeated setup versus shared code: independent projects repeat authentication, deployment, and styling work; a shared package can reduce duplication but introduces its own coordination and maintenance.
- Consistency: shared design conventions can create a coherent ecosystem, but separate implementations may drift without deliberate upkeep.
- Deployment autonomy: separate sites can be released independently, while a shared platform can centralise some operational work.
- Solo maintenance: every additional product adds responsibilities beyond its initial build, including documentation, testing, support, and distribution.
These are decision factors suggested by the architecture Murtaza describes, not measured comparisons between deployment models. His article does not provide benchmarks or evidence that the approach is faster, cheaper, or more reliable than alternatives.
What remains a plan, not a confirmed release
Murtaza lists Maniesta One as a future unified entry point, optional cross-product single sign-on, possible open-sourcing of Notes, Weather, and Play, and more writing. In the article, these are plans; it does not establish that they have since shipped.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
