Use OpenClaw on D3S
A practical guide to the D3S managed OpenClaw service: provisioning, AI configuration, approved plugins, runtime monitoring, and quota management.
1. What the D3S OpenClaw service provides
OpenClaw on D3S is a managed service, not a blank self-hosted install. D3S provisions the runtime, wires in gateway access, and gives you a control panel for configuration and operations.
You start by choosing a plan and billing term, create the site from the panel, then manage launch access, AI mode, Telegram, approved plugins, logs, and billing from the D3S dashboard.
Managed provisioning
OpenClaw sites are created through the D3S site flow with automatic provisioning or payment-gated activation, depending on the selected plan.
Built-in AI access
Managed mode lets you pick a D3S catalog/model from the dashboard without bringing your own API key.
Isolated runtime controls
Each site has its own runtime status, logs, gateway token, plugin state, and quota snapshot.
2. Provisioning flow
The public marketing page and the authenticated site flow connect into a single lifecycle:
Choose a plan
Start on the OpenClaw page, compare the available plans, and pick the billing term that matches your usage.
Create the site
In the site creation form, select OpenClaw, choose the plan and term, then submit the site request.
Clear billing if needed
Paid plans can enter pending payment until the invoice is settled. Eligible free tiers provision immediately.
Launch and manage
Once active, open the site detail screen to launch OpenClaw and access settings, plugins, logs, and billing details.
3. Dashboard surfaces you will use
After provisioning, the D3S panel becomes the control surface for day-to-day OpenClaw operations.
Site summary
Review status, launch URL, gateway token, invoice context, and OpenClaw-specific shortcuts from the site detail page.
OpenClaw settings
Switch between D3S managed AI, direct provider API keys, or OpenAI-compatible endpoints from the settings page.
Approved plugins
Search the approved package list, install a selected plugin, and review the latest command result and live runtime plugin inventory.
Runtime and billing
Check runtime health, fetch logs, see included and purchased AI quota, and jump into billing when payment is required.
Important operational note
Changing AI settings or raw config can queue a restart for active sites. Raw config is intended for advanced cases and overrides the standard form-based configuration.
4. AI configuration modes
D3S exposes three configuration paths so you can balance simplicity and control.
- D3S managed service: Recommended for most users. Choose from the managed model catalog in the dashboard and let D3S handle the runtime endpoint and service wiring.
- Direct provider API key: Bring your own supported provider key when you need a direct vendor connection while still using the managed OpenClaw runtime.
- OpenAI-compatible endpoint: Point OpenClaw to a custom compatible server URL, model name, and API key for advanced integrations.
Telegram setup
Telegram is the built-in channel setup surfaced directly in the panel. Configure both the bot token and the numeric user ID to enable notifications and workflows.
Raw JSON override
Use the raw configuration editor only when the standard settings page is not enough. Saving raw config keeps the override on the site and may defer normal settings behavior until you clear it.
5. Channels and integrations
The D3S service exposes a practical path for channel setup and extension instead of asking you to manage the full runtime yourself.
Telegram in the dashboard
The current first-class channel flow is Telegram. Its credentials live on the OpenClaw settings screen, so you can manage the connection without editing files on the server.
Approved plugin expansion
Additional capabilities are delivered through the approved plugin workflow. Search the allowlist, install a selected package, and verify the result from command status and live plugin data.
Managed rollout model
D3S controls what is exposed in the product so that new integrations and runtime actions can be released safely instead of leaving every environment fully self-managed.
6. Plugins and restricted commands
The plugin page is designed around controlled operations, not arbitrary shell access.
Search approved packages
Only packages in the D3S-approved list are presented for installation. Search by name or package to narrow the catalog.
Install the selected plugin
The panel submits a restricted OpenClaw install command for the chosen package and pins the package during installation.
Review output and live state
After the command runs, review status, attempts, exit code, captured output, and the live plugin list reported by the runtime.
Restricted commands are guarded by D3S. Install actions require an active site with runtime placement, and unsupported commands are rejected.
7. Runtime, quota, and billing
The guide is not complete without the operational controls that keep the service usable after launch.
Runtime status and logs
Use the site detail page to poll runtime status, view logs, and understand whether the controller can reach the assigned node.
Managed AI quota
OpenClaw sites show included quota, purchased quota, remaining balance, refresh schedule, and health of the remote quota snapshot.
Billing actions
If a site is pending payment or becomes past due, the panel links you back to billing so invoices and top-ups can be resolved.
Launch and token management
Active sites expose the launch URL plus the gateway token and token-sync actions used to keep the OpenClaw session connected.
8. Support and troubleshooting
When the normal controls do not resolve the issue, D3S keeps support inside the product workflow.
Ready to start with D3S OpenClaw?
Compare plans on the OpenClaw service page, then create your site and configure it from the dashboard.