Skip to content

Features

Everything strackt does for your app.

Deployment, previews, server work, recovery and automation, on servers in your own provider account. Supported capabilities and current limits, in one place.

Deploy

  1. Bring your own servers

    Adopt fresh servers with at least 2 GB of memory from your provider, or order through strackt. Keep your account, region and bill. Adoption replaces the existing operating system.

  2. Git connections

    Connect GitHub through its GitHub App, or GitLab, Bitbucket Cloud and Gitea through webhooks. Pull-request previews and feedback in the pull request are GitHub-only today.

  3. Detected, then confirmed

    Runtime, extensions, database, cache, workers and scheduler are read from your repository. Review the proposal before anything is set up.

  4. Temporary hosting while you arrange servers

    Layover gives you a temporary place to start: 30 days on us, one per team, then €10 a month excl. VAT. Layover and provider costs.

  5. Zero-downtime deploys

    For Laravel zero-downtime environments, a push builds the next release while the current one keeps serving traffic. Migrations run before the switch and must remain compatible with the serving code.

  6. Editable deploy plans

    Add commands, reorder steps, and hook into start, success, failure or rollback. Override one deploy without changing the saved plan.

  7. Preflight and release checks

    Checks prepare the release before traffic switches. Release verification checks the serving app after the switch; persistent server errors can return it to a retained release. A warning can let a deploy continue when a check cannot run. The deploy sequence and its limits.

  8. Domains and HTTPS

    Every environment gets an HTTPS address. Attach your own domains; certificates are issued and renewed automatically. DNS and certificate health checks flag what needs attention.

  9. Databases on your servers

    MariaDB, PostgreSQL and Valkey (a Redis-compatible cache), set up with credentials for your app.

  10. Bring a WordPress site Beta

    Import an archive or start a fresh installation for a WordPress site you operate. The WordPress path.

Develop

  1. Environments for each stage

    Production, staging and your own environments have independent settings. GitHub previews have their own environment, database and review address; the sequence below shows their lifecycle.

  2. Configuration and secrets

    Use the environment editor with encrypted secrets and secret references. Secrets stay separate for each environment and are written to its servers on deploy.

  3. Your team, in the same workspace

    Invite teammates to the shared apps and servers. Spotlight (⌘K) searches the workspace.

  4. Laravel workers and scheduled tasks

    Repository detection covers queues, workers and the scheduler alongside PHP, database and cache requirements. The Laravel-specific setup.

The life of a pull request

A preview for every pull request.

Each GitHub pull request gets its own environment, database and address to share. Pull-request previews and deploy feedback in the pull request are GitHub-only today.

  1. 01

    Open PR

    feature/checkout

    Open a pull request to create a preview environment.

    Source environment
    Production
    Cleanup rule
    When the PR is merged
  2. 02

    Build

    Building

    Build and deploy the branch into its own environment.

    Database
    Separate from production
    Branch
    feature/checkout
  3. 03

    Review

    Ready to review

    Share the preview URL and test the change before merging.

    URL
    shop--pr-42.example.test
    Production
    Unchanged by preview deploys
  4. 04

    Merge and clean up

    Removed

    Merge the branch back into main. Production follows its deploy settings; the preview is removed using the configured cleanup rule.

    Cleanup rule
    PR merged
    Temporary environment
    Released
Cleanup follows your settings

A closed PR does not trigger cleanup unless that rule is enabled.

Delete on merge
Enabled
Delete on close
Disabled
Idle timeout
Disabled in this example

Illustrative preview. Cleanup on merge, close or idle time follows your settings; the preview URL is an example.

Operate

  1. Security fixes on running servers

    We apply security fixes within 24 hours, onto the running servers. Most need no reboot. Advisories are matched against recorded package versions; package fixes are reviewed and approved by an operator. From advisory to running.

  2. Operating-system and supported-software upgrades

    Operating-system upgrades are prepared from the recorded setup and checked for compatibility. Runtime and database upgrades follow supported versions and their upgrade policy; some need an explicit redeploy.

  3. A recorded server setup

    Packages, services, users and firewall rules are recorded. Each managed configuration change brings the setup back into line. How the known state works.

  4. Reboots with separate rules

    Fixes arrive continuously. Routine reboots land in the window you pick, in your timezone, with seven days’ notice. You can postpone once. Expedited security reboots use your window after a 72-hour lead time. An actively exploited flaw overrides the window: reboot within 24 hours, with four hours’ notice. Reboots briefly interrupt service. Reboot windows.

  5. Backup destinations and health Beta

    Local snapshots on supported storage, copies on other servers, and encrypted copies in your own storage protect against different losses. Off-server copies need a configured destination; you choose the schedule and retention. We check runs and storage health, not restore tests. Own-storage backups are in beta. Backup responsibilities and limits.

  6. Activity, results and notifications

    Watch deploys and setup work in live activity. The history records what changed, who started it, timing and the result. Successful automatic updates stay quiet; failures notify you. Updates that changed nothing stay out of the list.

  7. WordPress inventory and protected updates Beta

    Inspect core, plugin and theme versions and vulnerability checks. Opt-in site updates take a checkpoint, apply the update and check health. The protected site-update sequence.

  8. A person when automation cannot finish

    An automation failure alerts JP to investigate. Beta support is asynchronous. Beta support and expectations.

Recover

Choose the recovery point for what changed. Code, application files, database and server setup have separate recovery actions.

  1. A bad release → previous code release

    Return to a previous application release on zero-downtime environments. The database stays current; check that the selected code can run against it. Database recovery is a separate action.

  2. Changed data → a restore point

    Restore application files from a completed checkpoint on supported storage. The original storage must still be available; later changes can be lost. Database recovery is separate. Completed backups in your own storage remain recoverable with your key and stock restic (Beta).

  3. Lost servers → rebuild and restore Beta

    Replace lost servers under their existing records: set up the replacements, restore an available off-server copy and redeploy their environments. You choose and confirm the replacement; it is not automatic. Copies need a configured destination. Available to teams with the beta enabled.

  4. Database recovery is a separate action

    After a bad migration, recover the database from an available database snapshot. A code rollback or application-file checkpoint does not rewind the database. Recovery choices.

  5. Return to the previous server setup

    Previous built configurations stay available. A failed activation health check returns to the previous setup; configuration rollback changes the setup, not your application data. Configuration recovery.

Access and automate

  1. Short-lived signed SSH

    Open a shell with strackt ssh. Access certificates are signed when needed and expire after at most one hour. Server access and permissions.

  2. Private networking and isolation

    Apps and databases across servers, including across providers, communicate over an encrypted network, without opening private service ports publicly. Per-application isolation, per-server firewall rules and source allowlists keep access explicit.

  3. CLI and REST API

    Deploy and roll back, manage environments, configuration, secrets, domains, logs and checkpoints. Tokens are workspace-scoped and have permissions for the work you allow. Server setup, firewall, maintenance-window and backup controls remain in the dashboard.

  4. Your scripts, CI and coding agent

    Use structured JSON, the command schema, typed errors and non-interactive commands. The CLI can wait for a deploy result and reuse an idempotency key for retries. Agent sessions are recognized; non-interactive mode is not an approval check. Install it and run a real workflow.

  5. Signed webhooks Beta

    Receive signed events and inspect delivery history when deploys, environments or servers change.

  6. Managed commands and WP-CLI Beta

    Run a managed command or WP-CLI against a selected environment.

  7. Take over with your own keys Beta

    A checked handover and credential cleanup let you keep the running setup, your servers and your access. The handover is not enabled in every workspace. The exit procedure and its conditions.

Grow

  1. Your app wants room to grow. Beta

    Give the app, its database and its workers room on separate servers. It is still one app, with one fee.

  2. The database outgrew its server. Beta

    Move the database to bigger servers with its data, then switch the apps that use it. Service migration is in beta.

  3. Staging shouldn't share a server with production. Beta

    Run production, staging and pull-request previews on separate servers, each with its own settings. Previews are GitHub-only.

  4. More traffic than one server.

    Run the app across servers behind one public entry point. strackt checks first that the app is safe to split. That entry point is still a single point of failure.

  5. Moving to another provider, or another country. Beta

    Move an environment to servers at another provider, with its data and history. You confirm the cutover; serving pauses while the final changes move.

  6. Shared services across applications

    Applications can use shared services rather than each requiring a separate database or cache service. What belongs to the app fee.

Scope and limits

  1. Supported stacks Beta

    Laravel, plus WordPress, plain PHP, Symfony, Node.js, Next.js and Nuxt in beta. WordPress is managed as an operated site.

  2. GitHub previews

    Pull-request previews and deploy feedback in the pull request are GitHub-only today.

  3. Infrastructure limits

    No scale-to-zero, bundled CDN, multi-region failover, Docker or Compose deployment, or your own Kubernetes. Bring a CDN or S3 storage when you need one.

  4. The apps you build

    strackt is for the apps you build and WordPress sites you operate. For installing packaged software, Coolify is a better fit. Its catalogue reference was verified on 29 October 2026.

  5. Dashboard controls

    Firewall, server setup, maintenance windows and backup controls remain in the dashboard. The CLI covers the application lifecycle; it is not an interface to every platform setting.

  6. Price and beta support

    €5 per app, per month, excl. VAT; the first app is on us. Your providers bill for servers and backup storage. Beta support has no published SLA. Pricing. What beta means.