Skip to main content

​
Optional Deployment Automation

​
Overview

Skip the DevOps headache. After your code passes acceptance, Fiftyknots can deploy your application to production infrastructure automatically. The platform analyzes your deliverable, recommends the right cloud setup, handles provisioning, and gives you a secure handover package with everything you need to own and operate your application. You pay once for deployment and control your ongoing hosting costs.

​
Step-by-Step Guide

  1. Review deployment eligibility - After your deliverable passes acceptance, navigate to the Deployment page (/deployment). The system displays whether your project qualifies for automated deployment.
  2. Get infrastructure recommendations - Click “Analyze for Deployment.” The AI scans your codebase and presents infrastructure options across AWS, Azure, and Google Cloud. You see three tiers (small/medium/large) with compute size, database type, storage requirements, and estimated monthly costs for each.
  3. Select your deployment tier - Choose the tier that fits your budget and scale needs. The platform shows cost accuracy within 15% of actual monthly hosting. Review the infrastructure breakdown - database type (PostgreSQL, MySQL, MongoDB, Redis), required third-party services (email, SMS, payment gateways), and domain configuration options.
  4. Configure deployment parameters - Fill in the secure configuration form with environment variables, API keys, and database passwords. Add your custom domain name if you have one - the system provides DNS instructions. The platform validates configuration completeness before proceeding.
  5. Review cost breakdown - Check the itemized costs: one-time deployment fee, infrastructure provisioning costs, and estimated monthly hosting. The deployment fee covers automated setup. Ongoing hosting bills come directly from your chosen cloud provider.
  6. Authorize payment - Click “Proceed to Payment.” Enter payment details via Stripe. Payment processes before deployment begins. You receive a payment confirmation email.
  7. Monitor deployment progress - Watch real-time deployment logs on the Deployment page. The system provisions cloud resources, deploys your code, configures environment variables, sets up HTTPS/SSL certificates, runs smoke tests, and configures logging and monitoring. 90% of deployments complete within 20 minutes.
  8. Receive handover package - When deployment succeeds, you receive an email with your handover package. It includes admin credentials, database passwords, API keys, deployment endpoints (URLs, API base paths, admin panels), deployment logs, configuration manifest, and a quickstart guide. The package remains securely stored for 90 days.
  9. Access your deployed application - Use the provided URLs and credentials to access your live application. Follow the quickstart guide to verify functionality and begin operations.

​
Common Questions

What cloud providers can I deploy to?
Fiftyknots supports automated deployment to AWS, Azure, and Google Cloud Platform. During the recommendation phase, you see options across all three providers with cost comparisons. Choose based on your preference, existing cloud relationships, or cost optimization. What happens if my deployment fails midway?
The system automatically rolls back infrastructure changes if deployment fails. You see error logs identifying what went wrong. No charges apply for failed deployments. You can fix configuration issues (like invalid environment variables) and retry without additional deployment fees. Can I trigger a rollback after deployment succeeds?
Yes. Within 24 hours of deployment, you can manually trigger a rollback to restore the previous stable state. Rollback completes within 5 minutes. Access the Deployment page, find your deployment record, and click “Rollback Deployment.” This helps if you discover runtime issues post-deployment. How do I handle monthly hosting costs after deployment?
Monthly hosting costs bill directly from your cloud provider (AWS, Azure, or Google Cloud). The deployment fee you pay to Fiftyknots is one-time and covers automated setup only. You own the infrastructure - manage it through your provider’s console, adjust resources as needed, or shut it down to stop costs. What if I lose access to my handover package credentials?
Contact support immediately through the support ticket system (/support). Provide your deployment ID and job details. The support team can regenerate access credentials or guide you through password reset procedures for your specific infrastructure setup. Do not attempt to recreate infrastructure manually.

​
Troubleshooting

Deployment stuck at “Provisioning Infrastructure” for over 30 minutes
Cloud provider API delays sometimes occur. Check the deployment logs for timeout errors or rate limiting messages. If logs show no progress for 30+ minutes, the system likely encountered a provider API failure. Click “Cancel Deployment” and retry. If the issue persists, escalate to support - provider-side outages require manual intervention. Smoke tests fail after code deployment succeeds
Your application deployed but isn’t responding correctly. Common causes: missing environment variables, incorrect database connection strings, or code expecting manual configuration steps. Review the smoke test failure logs to identify which endpoint or service failed. Update your configuration on the Deployment page and click “Redeploy with Updated Config.” The system reapplies configuration without rebuilding infrastructure. Estimated costs differ significantly from actual cloud provider bills
Fiftyknots guarantees cost accuracy within 15%, but provider pricing changes or unexpected usage spikes can cause variance. Review your cloud provider’s billing dashboard to identify unexpected charges - often traffic overages, data transfer costs, or third-party service fees. Adjust your infrastructure tier or configuration to control costs. Contact support if estimates were off by more than 15% due to stale pricing data. Cannot access deployed application using provided URLs
DNS propagation for custom domains takes 24-48 hours. If using a custom domain, wait for propagation or test with the provider-generated URL first. If the provider URL also fails, verify your deployment completed successfully - check deployment logs for “Deployment Complete” status. SSL certificate generation can take up to 10 minutes after deployment. If issues persist beyond 48 hours, check your domain’s DNS records match the instructions provided in the handover package. Client Review (/review/clientreview) - Before deployment becomes available, you approve or reject deliverables through Client Review. Only accepted deliverables qualify for deployment automation. This ensures you deploy quality code that meets your requirements. Escrow Dashboard (/escrowdashboard) - Deployment fees process through the escrow system. View deployment payment status, transaction history, and reconcile deployment costs against your project budget through the Escrow Dashboard. Data Room Detail (/dataroomdetail) - After deployment, store your handover package, infrastructure documentation, and deployment logs in your Data Room for long-term reference. This creates a permanent record of deployment credentials and configuration separate from the 90-day retention period.