Deployment
Deploy and manage projects
Deployment
Learn how to deploy and manage your Knitt projects with zero configuration.
Overview
Knitt handles deployment automatically. There's no build process, no deployment pipeline to configure, and no servers to manage. When you create content, upload media, or make configuration changes, they're instantly live.
This guide covers how deployments work, best practices, and strategies for managing different environments.
How Deployment Works
Instant Changes
Changes to content, configuration, and uploaded files go live immediately. There's no "deploy" button - updates are available as soon as you save them.
Global Distribution
Content and media are automatically distributed across a global CDN, ensuring fast load times for users worldwide.
Automatic Scaling
Your project automatically scales to handle traffic spikes. No configuration needed - it just works.
Zero Downtime
Updates are applied without any downtime. Your API and content remain accessible during changes.
Managing Environments
While Knitt doesn't have built-in staging environments, you can create separate tenants for different environments (development, staging, production).
Multiple Tenants Strategy
Create separate tenants for each environment:
Development: dev-myapp.knitt.app Staging: staging-myapp.knitt.app Production: api.myapp.com (custom domain)
Each tenant is isolated with its own data, API keys, and configuration. Test changes in development and staging before applying to production.
Content Syncing
Use the Knitt API to sync content types and configuration between environments:
// Export content types from staging
GET /v1/content/{staging_tenant}/types
// Import to production
POST /v1/content/{production_tenant}/typesAPI Keys & Environments
Each tenant has its own API keys. Use environment variables in your application to switch between environments:
# .env.development KNITT_API_KEY=dev_key_123 KNITT_TENANT_ID=dev-tenant-id # .env.production KNITT_API_KEY=prod_key_456 KNITT_TENANT_ID=prod-tenant-id
Never commit API keys to version control. Always use environment variables and keep production keys secure.
Deployment Checklist
Before deploying to production:
Test in staging environment
Verify all features work as expected with production-like data
Add custom domain
Configure your production domain and wait for SSL
Set up API keys
Generate production API keys with appropriate permissions
Configure webhooks
Update webhook URLs to point to production endpoints
Review permissions
Ensure API keys have the minimum required permissions
Backup content
Export important content before major changes
Monitoring
Keep track of your deployment's health and performance:
Dashboard Analytics
View API usage, request counts, error rates, and response times in your tenant dashboard.
Webhook Logs
Monitor webhook deliveries and failures. Debug integration issues with detailed request/response logs.
Error Tracking
Check API error logs to identify and fix issues quickly. All errors include timestamps and request details.
Best Practices
Use multiple tenants
Separate development, staging, and production environments for safer deployments.
Test content type changes
Schema changes can affect existing entries. Test in a non-production environment first.
Monitor API usage
Keep an eye on request counts and error rates to catch issues early.
Use webhooks for notifications
Set up webhooks to get notified of important events in your production environment.
Rotate API keys regularly
Update API keys periodically and revoke old ones for better security.
Rollback Strategy
While Knitt doesn't have built-in version control, you can implement rollback strategies:
Content Backup
Export content types and entries via the API before making major changes. Store backups for quick restoration if needed.
Configuration as Code
Store content type definitions and configuration in version control. Use the API to apply changes programmatically.
Blue-Green Deployment
Maintain two separate tenants. Update the "green" environment, test thoroughly, then switch your application to use it.
Next Steps
Last updated: February 7, 2026