KuboRunPer-project permissions
Permissions are limited by project and responsibility. Publishing one website does not need to grant access to the whole account.
Security
Access control and data protection.
Per-project permissions, encrypted credentials and checks before each deployment. Here is how each protection works.
Your credentials stay private
Credentials are stored encrypted and passed only to the operation that needs them. Their values are kept out of logs and history.
Failures stay visible
When an operation fails, the dashboard shows its status for you to review. An incomplete task is not marked as finished.
Isolation
Each project has its own network.
Your services have a separate project network and CPU and memory limits. Sharing a server with other customers does not mean sharing your project network.
Changes and recovery
Check changes and keep their history.
Permissions control who can change a project. History records operations, and health checks help identify failed deployments.
Verified releases
We verify package origin and integrity before installation.
Reliable history
The audit trail records who made each change without storing credentials or request contents.
Private management
Agents reach the management system through outbound connections. They do not need an exposed administration port.
Recovery
Backups before sensitive changes, health checks and coordinated rollback.
Review your setup
Have specific security requirements?
Tell us what you need: isolation, data retention, backups or permissions. We can review which configuration fits your project.
Ask about a requirement →