Skip to main content

deployment

Implementation & Deployment

Overview

This document summarizes the implementation work, architectural decisions, deployment strategy, and major milestones completed during Phase 1 of the Knest Project.

The objective of Phase 1 was to transform the initial project foundation into a scalable on-demand residential cleaning platform with a structured contractor onboarding system, centralized administration, secure payment workflow, and a deployment architecture suitable for future expansion.

⸻

System Architecture

A multi-application architecture was adopted to separate customer-facing services, contractor operations, administration, and marketing content into independent components.

The deployed solution consists of:

  • Customer Mobile Application Scaffold
  • Contractor Mobile Application Scaffold
  • Contractor Onboarding Web Portal
  • Administrative Dashboard
  • Backend API
  • Marketing Website
  • Database

Each component communicates through a centralized Laravel backend responsible for authentication, business logic, bookings, contractor management, and payment processing.

⸻

Domain Architecture

To separate business operations from public marketing, the project was deployed using dedicated subdomains.

Domain Purpose getknest.ca Public marketing website and landing pages app.getknest.ca Administrative platform, backend application and contractor onboarding

This separation provides several advantages:

  • Independent deployment of the marketing website and application.
  • Improved security by isolating operational systems.
  • Better scalability for future applications.
  • Simplified maintenance and version management.
  • Clear separation between public and authenticated users.

⸻

Project Foundation

Major implementation work completed includes:

  • Backend configuration and optimization.
  • Application scaffolding.
  • Environment configuration.
  • Database preparation.
  • Role separation between customers, contractors and administrators.
  • Modular application organization for future scalability.

⸻

Customer Booking System

The customer booking workflow was redesigned to support the residential cleaning business model.

Implementation includes:

  • Service selection
  • Property information collection
  • Estimated pricing
  • Booking creation
  • Booking management Scaffold

The booking workflow was structured to allow future expansion into additional service categories without redesigning the booking engine.

⸻

Contractor Onboarding

A completely redesigned contractor onboarding workflow was implemented to improve verification, service quality, and operational readiness.

The onboarding process includes:

  • Account registration
  • Email verification
  • Personal information
  • Contact information
  • Address information
  • Reference information
  • Service selection
  • Service area selection
  • Availability configuration
  • Identity document upload
  • Selfie capture
  • Terms acceptance
  • Application submission

The onboarding experience was redesigned as a structured multi-step workflow to improve completion rates while ensuring all required information is collected before administrative review.

⸻

Identity Verification

To improve trust and reduce identity fraud, an identity verification process was implemented as part of contractor onboarding.

The verification workflow includes:

  • Government-issued identification upload.
  • Selfie capture.
  • Image validation.
  • Administrative verification prior to approval.

Google MediaPipe was integrated to perform facial landmark detection during selfie capture, ensuring contractors submit clear, correctly positioned facial images before completing registration.

This approach improves image quality, reduces invalid submissions, and provides a more consistent verification process.

⸻

Administrative Review

A structured approval workflow was implemented for contractor applications.

Administrators can:

  • Review contractor information.
  • Verify uploaded documentation.
  • Validate identity information.
  • Approve or reject applications.
  • Request additional information.
  • Activate approved contractors.

Only approved contractors are permitted to access operational features within the Contractor Mobile Application.

⸻

Contractor Operations

Phase 1 implements the operational workflow required for approved contractors.

Features include:

  • Availability management.
  • Booking management.
  • Booking acceptance.
  • Service progress updates.
  • Scope verification.
  • Job completion.
  • Earnings tracking.

⸻

Payment Architecture

A centralized payment workflow was designed around secure payment collection and controlled contractor payouts.

The implementation payment strategy consists of:

  • Customer payment during booking.
  • Funds held by Knest until service completion.
  • Scope verification before work begins.
  • Additional payment collection when required.
  • Partial refund processing where applicable.
  • Contractor payout after successful job completion.

This architecture provides greater control over disputes, cancellations, pricing adjustments, and contractor settlements.

⸻

Administrative Features

Phase 1 includes centralized management for:

  • Customers
  • Contractors
  • Contractor applications
  • Services
  • Pricing
  • Payments reports
  • Reviews
  • Reports
  • Platform configuration

⸻

Technical Improvements

Several architectural improvements were implemented throughout Phase 1, including:

  • Repeated redesign of the contractor onboarding experience.
  • Multi-step registration workflow.
  • Identity document management.
  • Selfie verification using Google MediaPipe.
  • Structured contractor approval process.
  • Separation of marketing and application infrastructure.
  • Modular application organization.
  • Improved booking lifecycle scaffolding.
  • Secure payment workflow supporting pricing adjustments.
  • Scalable project structure for future expansion.

⸻

Deployment Strategy

Phase 1 adopts a centralized deployment model in which all operational applications communicate with a single backend responsible for business logic, authentication, bookings, contractor management, and payment processing.

The deployment architecture separates presentation, operational services, and backend processing, allowing each component to evolve independently while maintaining a unified data model.

⸻

Phase 1 Outcome

At the completion of Phase 1, the Knest Project delivers:

  • Public marketing website.
  • Contractor onboarding portal.
  • Contractor verification process.
  • Identity document management.
  • Selfie verification.
  • Administrative approval workflow.
  • Service configuration.
  • Administrative oversight.

The completed implementation establishes a scalable technical foundation capable of supporting future releases while delivering the core operational requirements of the Knest Project.