Product type
White-label, multi-provider home services marketplace source foundation.
White-label source package · Updated August 12, 2026
On-demand home services app script.
Launch a multi-provider home services marketplace with separate Flutter customer and provider apps, a web owner portal, and a connected API—without beginning from an empty project.
Source access, customization scope, deployment, and commercial terms are discussed directly.
An on-demand home services app script is a pre-built software foundation for customer booking, provider operations, and marketplace administration.
Monolith at a glance
A white-label marketplace foundation, stated plainly.
Monolith connects the customer, service provider, and marketplace operator around the same booking and job record. These facts describe the current source package and are intentionally consistent with the demo, documentation, and product schema.
Applications
Flutter customer app, Flutter provider app, and web owner and admin portal.
Core stack
Flutter, Node.js, Fastify, TypeScript, PostgreSQL, and web-based administration.
Primary workflows
Discovery, provider availability, booking, assignment, field progress, messages, quotes, payments, reviews, and support.
Best suited to
Entrepreneurs, agencies, and service businesses launching a branded marketplace.
Launch model
Working source plus buyer-specific branding, integrations, compliance, QA, hosting, and store release.
What is included
Customer, provider, admin, and backend—connected.
Monolith is a working multi-application product foundation, not a collection of disconnected interface templates.
Flutter customer app
Service categories, search, provider discovery, booking, visit status, support, payment choices, reviews, and service history in one branded app.
Flutter provider app
Separate access for provider managers and technicians, with schedules, availability, assigned visits, job actions, photos, quotes, messages, and earnings visibility.
Web owner portal
A business workspace for customers, catalogue, provider network, bookings, assignments, payments, support, branding, plans, and operational decisions.
API and database
A tenant-aware Node.js and Fastify API backed by PostgreSQL, with migrations, role boundaries, operational records, uploads, notifications, and audit history.
Real product applications
Three focused experiences.
One service job.
A booking begins in the customer app, moves through assignment and field work, and remains visible to the operator from request to payment and service history.
Customer books→Owner assigns→Provider completes→Customer pays
01
Web admin portal
Operate the marketplace.
Manage service content, customers, providers, availability, bookings, assignment, progress, payments, support, brand, and tenant controls.
Real owner workspace- Catalogue
- Provider network
- Booking operations
- Money and support
02
Flutter customer app
Discover, book, and follow service.
Customers browse categories and providers, build a complete request, choose availability and payment, then follow the visit and its history.
- Search and categories
- Provider choice
- Booking
- Payments
03
Flutter provider app
Manage and complete field work.
Provider managers and technicians see their workday, availability, job details, customer context, visit actions, evidence, quotes, messages, and earnings.
- Manager and technician roles
- Availability
- Visit workflow
- Job messages
From source to production
What is included—and what every launch still needs.
A serious marketplace is not production-ready merely because it compiles. Buyer-owned accounts, rules, compliance, testing, and release approval remain part of implementation.
Start from the working source foundation
Use the customer app, provider app, owner portal, API, database model, tests, and deployment documentation as the implementation baseline.
Apply the buyer's marketplace rules and brand
Configure services, operating areas, provider onboarding, commissions or fees, legal policies, identity checks, visual identity, domains, and app identifiers.
Connect production-owned services
Register Firebase apps, supply payment and messaging credentials, configure maps or tracking, choose media storage, enable monitoring, and validate webhooks and notification delivery.
Test, harden, and submit
Run end-to-end QA on real devices, complete privacy and security checks, prepare store assets, sign the releases, and submit the iOS and Android apps for review.
Buyer questions
Clear answers before the demo.
These details describe the current product honestly; the implementation proposal defines any additional integrations.
What is an on-demand home services app script?+
An on-demand home services app script is a pre-built software foundation for a marketplace where customers discover and book services, providers manage and complete jobs, and operators control the business through an admin portal. It reduces the amount of product, design, and engineering work required before customization and launch.
What is included in the Monolith source package?+
The package includes separate Flutter customer and provider applications, a web-based owner and admin workspace, a Node.js and Fastify API, a PostgreSQL data model and migrations, and connected workflows for catalogue discovery, provider availability, booking, job progress, messages, quotes, payments, reviews, support, and white-label configuration.
Is the app ready to publish immediately?+
The working product and source foundation are included, but every buyer still needs production configuration and release work. This includes buyer-owned service credentials, Firebase app registration, signing, hosted media, payment validation, privacy and legal details, security review, and App Store and Google Play approval.
Does it include both customer and service-provider apps?+
Yes. Customers receive a Flutter marketplace and booking app. Provider-company managers and technicians receive a separate Flutter app for assigned work, availability, visit progress, evidence, quotes, messages, and earnings visibility. Business owners use the web portal.
Can the platform be white-labeled?+
Yes. The architecture separates tenant data, branding, catalogue, subscriptions, licenses, and entitlements. Brand assets, service content, credentials, domains, bundle identifiers, and store listings are configured for the buyer during implementation.
Who is the Monolith app script designed for?+
Monolith is designed for entrepreneurs, software agencies, and established service businesses that want to launch a branded, multi-provider home services marketplace without designing every customer, provider, operator, API, and database workflow from the beginning.
Are Google Maps and Stripe Connect payouts included?+
The current product includes job-location and tracking workflows plus customer payment integration paths. A production Google Maps implementation and automated marketplace payouts such as Stripe Connect require buyer-specific accounts, compliance choices, credentials, webhooks, and launch validation; they are not represented as zero-configuration features.
See the working marketplace
Review the customer app, provider app, admin portal, and launch scope.
Message us with your target market, required integrations, and branding. We will respond with a demo and implementation estimate.
Request the live demo