Deployment & Support
Deployment, Cloud Setup and Post-Launch Support
Your website or application may work in development but still need hosting, configuration, connected services and a clear handover before it can be released. My Faces Production prepares and deploys websites and web applications, configures included APIs and databases, and prepares mobile builds. The agreed scope defines what will be released, which accounts and materials you provide, and what support follows launch.
Suitable deployment paths
The right route depends on what has been built, the services it connects to and the accounts that will own the deployment.
-
Websites and web applications
Suitable web projects can be configured and deployed to Firebase Hosting or Vercel. Other hosting or cloud platforms can be considered when the application's requirements call for a different setup.
-
APIs and databases
When backend and database deployment is included, the work can cover the relevant server or cloud setup, API URLs, environment variables, application settings and service integrations.
-
Mobile application builds
Mobile builds can be prepared and app-store submission assistance can be provided when agreed. The client supplies the Apple Developer or Google Play Console accounts, verification details, listing information and required privacy materials. Publication remains subject to the store's review and approval.
From project build to deployed application
-
01
Review the release requirements
The project requirements, build configuration, environment variables and available deployment instructions are reviewed before the release setup begins.
-
02
Prepare the environment
Required application settings, API addresses and included service integrations are configured for the chosen deployment environment.
-
03
Deploy the agreed components
The website or web application is deployed to the selected host. Included APIs and databases are deployed to the applicable server or cloud service.
-
04
Check the deployed version
The development team checks that the application loads and that the agreed core workflows operate in the deployment environment.
-
05
Review and hand over
The client can inspect the deployed application and agreed workflows before acceptance. Identified issues are corrected and checked again under the project terms.
What you receive at handover
The concrete handover depends on the development agreement, but the deployment engagement can provide:
- A deployed website or application link, or a prepared mobile build, according to the agreed release.
- The project and environment settings configured within the agreed scope.
- Applicable setup, environment or deployment instructions included in the project.
- Agreed account access or repository access, while keeping client-owned business accounts under the client's control.
- Source code and project files when custom development has been purchased or source delivery is included in the agreement.
How the result is reviewed before acceptance
The development team reviews implemented functionality, user flows, interface behaviour and responsiveness. RestaurantFlow provides a representative example: its menu and table-ordering flow, order details, configured billing calculations and layouts at different screen sizes are checked. Issues found during review are corrected and checked again. The client can inspect the working interface, implemented features and agreed workflows before acceptance. Independent assessment, formal certification, extensive automated coverage or a written test report is included only when specifically agreed.
Accounts, external costs and responsibilities
Deployment works best when ownership and access are settled before release. Clients should retain ownership of their domain, hosting, cloud and app-store accounts wherever possible.
- The client provides the required account access, domain or DNS access, API keys, service credentials and account-owner verification.
- Hosting subscriptions, cloud usage, domains and third-party service, licence, payment or store fees remain the client's responsibility unless the agreement states otherwise.
- Only the integrations, platforms and application components named in the scope are included. Additional systems or release targets require a separate estimate.
- Delivery timing can be affected by unavailable access, client materials, feedback or approval by an external provider.
- Ongoing cloud management, monitoring and backups are not part of deployment unless they are explicitly included.
Define post-launch support before release
Post-launch support may be included in the project or priced separately. The agreement should state its duration, included hours or tasks, charges, exclusions and communication expectations.
There is no universal support period or unlimited maintenance arrangement. Response expectations are agreed for each project; no fixed response-time or 24/7 commitment applies across every engagement.
-
Defects in delivered functionality
Problems in the agreed delivered functionality are reviewed and addressed according to the project's support terms. A new requirement or a change to existing behaviour is treated separately.
-
Application maintenance
Dependency updates, compatibility work and technical improvements require an agreed maintenance scope.
-
Monitoring and ongoing operations
Application monitoring, cloud-resource monitoring, backups, performance checks and continuing deployment management are separate services unless expressly included.
-
New features and enhancements
Additional integrations, interface changes, features and expanded workflows are discussed and estimated as further development.
Inspect working product interfaces
My Faces Production publishes owned product demos covering restaurant operations, laboratory administration, salon booking, grocery delivery, ecommerce, pet-service discovery, property software and POS interfaces. These are product demonstrations rather than customer implementations or evidence of measured business results. They let you inspect existing interface and workflow examples before discussing a separately scoped project.
Start with what needs to be released
You do not need to choose a cloud platform or specify every technical component before starting a discussion. Share whether you already have a website or application, what needs to be available after launch and any accounts or services already in use. If you are not sure about the hosting, architecture or support arrangement, say so; those details can be clarified while the scope is defined.