QuikDB Compute

QuikDB Compute deploys applications from GitHub repositories and manages their configuration, runtime logs, routing and plan-based capacity.

Supported source paths

QuikDB can deploy an existing application as-is when its source and runtime contract are clear:

• an application-owned Dockerfile;
• supported project files with reviewed build and start commands; or
• an explicit quikdb.json configuration.

The dashboard detects likely settings, but it does not promise that every framework or repository layout needs no changes. Review the branch, service directory, build command, start command, port and environment variables before deployment. Unsupported or incomplete configurations fail truthfully instead of being presented as converted applications.

How it works

1. Connect GitHub and select the repositories QuikDB may read.
2. Choose a repository, branch and service directory.
3. Review the detected settings and add required environment variables.
4. Deploy and follow the build and runtime logs.
5. Operate the live application through redeploy, domain and resource controls.

A successful deployment receives a QuikDB URL. Custom-domain hosting with managed HTTPS is currently onboarded by QuikDB for selected supported users; public self-service will open later.

Current services

• Build and runtime logs for deployment diagnosis
• Environment variables stored outside the repository
• Limited-availability custom-domain routing with QuikDB-managed HTTPS
• Managed PostgreSQL for owned QuikDB deployments
• Plan-based replicas, capacity and sleep behaviour
• Bounded Agent Access pilot for pre-registered clients and approved reads

QuikDB domain registration is still a gated pilot. Agent Access does not provide unrestricted database, secret or mutation access.

Getting started

1. Open compute.quikdb.com.
2. Connect GitHub.
3. Choose a repository and review its settings.
4. Deploy and follow the logs.

Read Deploying Your App for the full workflow.