The control plane for every application, service, and database you run—self-hosted on your own infrastructure.
git push origin main
Cynone brings deployment, runtime, data, access, and signals into one workspace while keeping infrastructure choices explicit. Edge delivery, function-style runtimes, and scaling appear when the connected infrastructure supplies them.
Source delivery
Connect public or private repositories, preserve branch and commit context, and trigger repeatable application builds.
main
production8e2f41a · deploy queued
Preview environments
pr-184.preview.example
Isolated branch configuration
Delivery layer
Attach the CDN or global ingress provider you operate. Cynone keeps domains, TLS, and application routing connected to the release.
Ingress
Runtime
Signals
Workloads
Run web processes, queues, scheduled jobs, and supporting services with separate commands and resource controls.
Data plane
Provision and operate supported data services beside the applications that use them, with backups and lifecycle controls in context.
Configuration
Separate preview and production values, keep sensitive data masked, and make configuration changes explicit.
APP_ENV
production
plain
DATABASE_URL
••••••••••••
secret
FEATURE_CHECKOUT
enabled
plain
Route domains and manage certificate lifecycle.
Keep resource operations aligned with workspace roles.
Use function-style runtimes only where the connected deployment model supports them.
Operations
Read deployment and runtime output alongside health and resource signals.
GET /health 200
queue:work processing
backup scheduled
Apply replicas and capacity behavior only on compatible infrastructure targets.
Connect source once, let every commit create traceable deployment context, and choose the runtime topology that fits your infrastructure.
Select source
Example repository connection
example/api-service
Private repository
8e2f41a · current production
6b97c0d · preview candidate
Commit context
Handle idempotent webhook delivery
Example Author · just now
Deployment 215
feature/billing-events · 6b97c0d
00:01 repository cloned at 6b97c0d
00:04 framework detected: Laravel
00:12 dependencies restored from cache
00:31 container image assembled
00:37 health check responded
00:38 preview domain attached
Preview URL
billing-events.preview.example
Production
api.example.com
Trigger
Git push
Runtime topology
Example multi-target architecture
Gateway
TLS + routing
Runtime
Apps + workers
Data
Managed services
Replicas
Configure on compatible targets
Delivery
Attach your preferred edge network
Signals
Keep health and logs in context
Model ingress, runtime, data, and signals as connected systems. Optional global network and scaling layers follow the infrastructure you attach.
HTTPS ingress
Optional CDN / gateway
Web + workers
State + dependencies
Health + logs
Trigger a real deployment through the authenticated API, then inspect build detection, configuration, preview URLs, and logs in the workspace.
# install an API client if needed (Debian / Ubuntu)
sudo apt-get install -y curl
# one-time shell setup
export CYNONE_URL="https://your-instance.example"
export CYNONE_TOKEN="••••••••••••"
# deployment command
curl -fsS -X POST \
"$CYNONE_URL/api/v1/deploy?uuid=app_uuid" \
-H "Authorization: Bearer $CYNONE_TOKEN"
# example response
✓ Deployment queued
deployment_uuid: dp_01jexample
Detected framework
Environment
Keep build cache, runtime configuration, and resource controls close to the deployment that uses them.
Inspect release history, logs, backups, and rollback context while defining reliability objectives around your infrastructure.
Organize teams, projects, and environments with role-aware access to production operations.
Use encrypted secrets, TLS domains, API token abilities, and explicit confirmation for sensitive actions.
Cynone manages the control-plane workflow. Your servers, networks, credentials, and provider configuration remain explicit parts of the operating model.
Email/password, available OAuth providers, two-factor challenges, and recovery codes.
Team roles, resource policies, and scoped API abilities for read, write, and deploy operations.
Masked secret values and encrypted storage for supported sensitive fields.
Custom domains, proxy routing, and certificate lifecycle on connected infrastructure.
Cynone adapts to the operating model configured for your instance. Review the available options in your workspace or plan an enterprise rollout with the engineering team.
Self-managed
Operate Cynone on servers and providers you control. Infrastructure and operations costs remain with your chosen vendors.
Start deployingEnterprise
Discuss team structure, infrastructure topology, security boundaries, and support requirements before rollout.
Talk to an engineerMake the first deployment
Connect a repository, choose your infrastructure, and keep every deployment decision in one operational workspace.