Skip to main content

​
Optional Deployment Automation

​
Overview

Ship your accepted deliverable to production infrastructure without writing deployment scripts or wrestling with cloud provider consoles. Optional Deployment Automation analyzes your code, recommends the right infrastructure, handles provisioning, and delivers a complete handover package with credentials and endpoints - so you can focus on building traction instead of managing servers.

​
Step-by-Step Guide

  1. Request deployment after acceptance
    • Navigate to your project dashboard after your deliverable receives acceptance
    • Select “Deploy to Production” from the project actions menu
    • The system analyzes your codebase to identify infrastructure requirements
  2. Review infrastructure recommendations
    • View recommended deployment tiers (small, medium, large) with resource specifications
    • Compare estimated monthly hosting costs across AWS, Azure, and Google Cloud Platform
    • Review detected requirements: compute size, database type (PostgreSQL, MySQL, MongoDB, Redis), storage, and third-party services (email, SMS, payment gateways)
    • Select your preferred cloud provider and deployment tier
  3. Configure deployment parameters
    • Complete the secure web form with environment variables and API keys
    • Provide custom domain name if desired (DNS configuration instructions included)
    • Upload SSL certificates or request automatic HTTPS setup
    • Validate configuration completeness before proceeding
  4. Approve costs and authorize payment
    • Review itemized cost breakdown showing one-time deployment fee and estimated monthly hosting costs
    • Process payment via Stripe to authorize automated deployment
    • Receive confirmation that deployment will begin
  5. Monitor deployment progress
    • Watch real-time deployment status on the Deployment page (/deployment)
    • View detailed logs showing infrastructure provisioning, code deployment, and configuration steps
    • Receive notification when deployment completes (typically within 20 minutes)
  6. Access your handover package
    • Download the complete handover package from your email or the deployment dashboard
    • Access admin credentials, database passwords, API keys, and deployment endpoints
    • Review the quickstart guide for accessing your deployed application
    • Note the 90-day secure retention period for credential recovery

​
Common Questions

What cloud providers do you support? We support AWS, Azure, and Google Cloud Platform. The system recommends the best fit based on your codebase requirements, but you can select your preferred provider during configuration. How accurate are the cost estimates? Cost estimates are within 15% accuracy of actual monthly hosting costs. The system accounts for compute, database, storage, and networking requirements detected in your code. Final costs may vary based on actual usage patterns and provider pricing changes. What happens if deployment fails? If deployment fails during execution, the system automatically rolls back all infrastructure changes to prevent partial deployments. You’ll receive a detailed error report and can retry after addressing any configuration issues. No charges apply to failed deployments. Can I manually trigger a rollback after deployment? Yes. Within 24 hours of deployment completion, you can manually trigger a rollback that restores the previous stable state within 5 minutes. This is useful if you discover issues after initial deployment. What if I need manual configuration steps that can’t be automated? The deployment process handles standard infrastructure and configuration automatically. If your code requires specialized manual steps, the system flags these during analysis and provides detailed instructions in the handover package. You can complete manual steps after automated deployment finishes.

​
Troubleshooting

Deployment stuck at infrastructure provisioning If deployment progress stalls during cloud resource creation, the system will automatically time out and roll back after 30 minutes. Check your cloud provider’s service status page for outages. If provider APIs are experiencing issues, wait for service restoration before retrying deployment. Invalid environment variables causing runtime failures If your deployed application fails to start due to incorrect environment variables, access the deployment dashboard and select “Update Configuration.” Modify the problematic variables and trigger a redeployment. The system will update your running application without reprovisioning infrastructure. Lost access to handover package credentials Handover packages are retained securely for 90 days. If you lose access to your credentials, visit the Deployment page (/deployment) and download the handover package again using your Fiftyknots account credentials. Contact support if the retention period has expired. Actual costs significantly different from estimates If your monthly hosting costs vary more than 15% from estimates, review your application’s actual resource usage in your cloud provider console. Unexpected traffic spikes, data transfer, or third-party service usage can increase costs. Request a cost analysis review through the deployment dashboard to identify optimization opportunities. Escrow Dashboard (/escrowdashboard) - Review how deployment costs are managed through the escrow system. Deployment fees and initial hosting costs are held in escrow until successful deployment verification, protecting your investment. Client Review (/review/clientreview) - Access the acceptance workflow that precedes deployment. Only deliverables that pass client review qualify for optional deployment automation, ensuring you only deploy validated code. Data Room Detail (/dataroomdetail) - Store deployment credentials, infrastructure documentation, and monitoring reports in your secure data room. The handover package automatically saves to your data room for long-term access beyond the 90-day retention period.