Use case · Development environments
Create a repeatable workspace without tying the project to one machine.
Shared Regular for general work; High Frequency for build-heavy workflows.
Compare suitable serversWhy use a cloud server for development and testing?
A cloud development server gives a team a consistent Linux environment that stays available beyond one laptop. It is useful for previews, integration testing, build workers, and temporary project infrastructure that needs a stable address and repeatable setup.
What the server can support
- Standardize a team environment
- Run previews and integration services
- Rebuild from a supported Linux image when needed
Decide before deployment
- Whether data must persist between rebuilds
- Access control and SSH-key handling
- Cost of leaving temporary environments active
Representative architecture
Keep each dependency visible.
This sequence is a planning model, not a prescribed topology. Change it when the application’s measured request and data paths require a different boundary.
- 01Developer access
- 02Shared Linux workspace
- 03Preview services
- 04Disposable or protected project data
Selection criteria
- Decide what must survive a rebuild
- Use individual SSH keys instead of shared credentials
- Match build concurrency and cache size to CPU, memory, and storage
Failure modes to test
- An environment becomes a hidden production dependency
- Shared credentials remove individual accountability
- Unbounded build caches consume storage
Catalogue connection unavailable
No configuration is being guessed.
Current active configurations could not be verified. Use the decision criteria on this page, then retry the catalogue when the connection recovers.
Recovery implication
Decide what must return before choosing how to protect it.
Keep source, environment definitions, and secrets outside the server. Rebuild the workspace from documented inputs instead of treating the machine as the only copy.
Application, configuration, credentials, and database.
Server-level and application-aware recovery inputs.
Recover without overwriting the source by default.
Check data, dependencies, access, and application behavior.
Choose from evidence, then observe
The suggested family is a starting point, not a guarantee of application performance. Test the software with representative traffic, monitor the constrained resources, and keep application-aware backups. Vloxt exposes eligible server controls and current catalogue choices; the application architecture remains yours.
Read the complete server-selection guide or explore platform features.