Get Started
Accounts
- Cloud accounts
- Connect GitHub account
Guides
- Languages
- Single Page Applications
Environment
- What's inside?
- Create environment
- Customise environment
- Delete environment
- Shared responsibilities
- Services
- Extend using Terraform/Pulumi
- Managed cloud services
- Monitoring
- Infrastructure Resources
- Disaster Recovery
- Eject out
Troubleshooting
Bring your helm charts (Deprecated)
- First Steps
- Publish Helm Charts
- Tutorials
- Databases
- Database Migration
- Environment Variables
- Multiple Helm Charts
Support
Frequently Asked Questions
Yes. When you stop using LocalOps, app environments are left as they are, for your team to manage them manually or by other means. Check how to eject to learn more.
Yes, if you have containerised your application and made a a Kubernetes Helm Chart for it. However, if you use managed cloud services such as Amazon S3, you are supposed to provide alternate implementations to run in other cloud providers such as GCP or Azure.
Yes. Unlike PaaS services such as Heroku, you are free to pick and use any database to build your application. As long as you can find a docker image for it to declare it within Helm Chart as your dependency, LocalOps can spin up an App environment with that database, in any cloud.
Yes. You are free to pick any SPA framework to build your Front end. Check Single page apps to learn more.
There is no fool-proof technical way to hide/obfuscate your code. If your service is written in compiled languages, it helps. Otherwise we’d suggest you to address this legally in your Services agreement with customer.
LocalOps tags all cloud infrastructure resources by two standard names. *-id and *-name. You can locate them in App
Environment settings page. Using these tags, anyone can filter down AWS resources in AWS console and find out their
cost.
LocalOps will soon show a monthly cost estimator under each app environment’s details page.
LocalOps creates App environments on the connected cloud accounts. Owners of the cloud account are billed by cloud provider for the resources provisioned.
Was this page helpful?