dokwe.com

What It Is

Dokwe is a deployment and operations platform for developers and platform engineering teams. Its core tagline is “Deploy from git. Run your fleet. Stay in control.” Based on the crawled content, it covers both Git-driven application delivery and a Fleet operations console, spanning Day-2 operations scenarios such as servers, clusters, workloads, health checks, alerts, patching, failover, and disaster recovery drills.

Core Capabilities

On the build side, Dokwe supports connecting GitHub repositories, selecting branches, and automatically building and deploying after subsequent pushes. Its application primitives include Projects, Services, Functions, Environments, and Cron Jobs. At the service layer, it mentions Postgres + pgvector, Redis, and RabbitMQ, which can be provisioned per workspace with one click. Environments support variables, domains, deployment targets, maintenance mode, and container logs.

Operations is where Dokwe puts more emphasis. Observability provides real-time metrics, error capture, AI event analysis, and log streaming. Deployments & Logs supports build logs, runtime logs, and rollback by commit. The Fleet console can manage Hosts, Clusters, systemd units, Windows services, IIS sites, and containers. It also supports TCP/HTTP/command/file/log-based health checks, Slack/Webhook/SMTP/SMS alerts, maintenance windows, rolling patches, failover, DR drills, and CSV/PDF audit exports.

AI, API, and Ecosystem

Dokwe includes built-in AI Agents, including agents for error triage, security, and optimization, with configurable scheduling, token budget, and a findings inbox. RAG Setup can embed repo code, failed deployments, and deployment summaries into pgvector, allowing Ask AI to answer based on project state. For integrations, it explicitly supports GitHub Actions, HMAC-SHA256 signed Webhooks, Anthropic/OpenAI/Google model providers, and a Skills Marketplace. At the API layer, it provides a REST reference and workspace API keys.

Pricing and Limitations

The main content does not provide pricing, plans, free quotas, payment methods, or SLA details, nor does it state whether the product is open source. Although it clearly supports Bring Your Own Server—installing an agent on a Linux host via curl and choosing either cloud or BYOS deployment targets—it does not clarify whether the control plane can be fully self-hosted. Language and framework support is also not listed; the only clear takeaway is that it targets containerized applications and function-style jobs.

Pros, Cons, and Who It’s For

Its strengths are end-to-end coverage: it can handle Git-based deployment as well as server fleet operations, auditing, rollbacks, and disaster recovery. This makes it attractive to teams that care about retaining control over their infrastructure. The downside is that the publicly available information still feels more like a documentation outline; its business model, available regions, open-source status, and ecosystem breadth remain unclear. Dokwe is suitable for small to mid-sized teams or platform engineering teams that have their own servers and need standardized releases plus operations auditing. If you only need frontend hosting, Vercel or Netlify may be lighter options. If you are looking for a self-hosted PaaS, it is worth comparing with Coolify, Dokploy, and Portainer.

Access from China

The crawled content does not provide information about access from mainland China, network nodes, ICP filing, RMB payments, or local payment methods, so china_access can only be marked as unknown. For teams deploying it in China, it is recommended to first verify connectivity to dokwe.com, GitHub integrations, model provider APIs, and Slack/SMS channels, while preparing Coolify, Dokploy, or a self-built CI/CD pipeline as fallback options.