01 / D1 DATABASESClear data.
Clear data.
Deliberate changes.
Browse tables, run SQL, and review edits before committing. Check original values to catch conflicts.
Explore the D1 workflow BUILT FOR YOUR WORKFLOWWINDOWS / CLOUDFLARE
Cloudflare.
At your fingertips.
Your data, files, and logs. One desktop workspace.
VeDock brings everyday Cloudflare work closer — right to your Windows desktop.
01 / A WORKFLOW, IN MOTION
ILLUSTRATIVE DEMO · SAMPLE DATAD1 / Review your changes before committing.
AUTOPLAY / ILLUSTRATIVE WORKFLOWAn illustrative walkthrough using sample data.
02 / THE EVERYDAY ESSENTIALSLESS FRICTION. MORE CONTEXT.
Stay in
your flow.
A familiar place for the work you do every day. From a single database row to the last file in your bucket.
02 / R2 STORAGEFrom your desktop.
From your desktop.
To the right bucket.
Browse, upload, and download. Resolve collisions before overwriting. Check lock rules and Data Catalog before deleting.
Explore the R2 workflow03 / WORKERS LOGSEvery event.
Every event.
In context.
Follow live logs or query a Worker’s history. Carry a selected value into D1 to keep investigating.
Follow the event stream03 / A CLOSER LOOK AT D1FROM A ROW TO A REASONED CHANGE
Make the edit.
Keep the context.
Sometimes the work is one cell. Sometimes it’s a query. Move between both without losing sight of the database you’re working in.
01
Explore first. Browse tables and views, find a value on the loaded page, or write the SQL you need.
02
Review the difference. Stage table edits and see what will change before committing.
03
Keep useful work. Revisit query history or export a result as CSV.
04 / OBJECTS, ORGANIZEDR2 STORAGE
A place for every file.
A path for every task.
Move files from your desktop to a bucket. Keep the destination clear and the progress visible, from the first upload to the final result.
Upload. Download. Continue.
Drop files into the workspace, follow their progress, and find the result in Jobs.
A name collision is a choice.
Keep the existing object or explicitly approve an overwrite. The decision stays with you.
Deletion starts with a plan.
Fix the scope, check lock rules and Data Catalog, then confirm the number of objects to delete.
BEFORE DELETEScope→Scan→Preflight→Confirm→Report
05 / FOLLOW THE THREADWORKERS OBSERVABILITY
See it happen.
Find it again.
Stay with a live request or look back at a specific moment. Two perspectives on the same Worker.
LIVE
The present, as it arrives.
Follow requests and console output. Filter the stream or pause the display while you inspect an event.
HISTORY
The moment that matters.
Choose a time range, add a search, and query one Worker. Pick up the investigation from a returned event.
History availability depends on your Cloudflare permissions and retention. VeDock keeps viewed log events in memory, not in a local log archive.
06 / ROOM FOR YOUR PROJECTSChange accounts.
Change accounts.
Not your rhythm.
Keep account context visible as you move between databases, buckets, and Workers. Open the work you need without blending one project into another.
ONE APP. DISTINCT CONTEXTS.
Your chosen account stays attached to the workspace and its actions.
07 / DESIGNED TO KEEP YOU IN CONTROLLOCAL FIRST.
Your machine.
Your permissions.
Sign in with OAuth.
Choose the modules and access levels you need. No API tokens to paste into VeDock.
Know the account. Know the action.
Each workspace stays tied to its account. Review changes before they happen, and reconcile uncertain outcomes before trying again.
Stored locally. Connected directly.
Credentials, cache, and job history stay on your machine. VeDock connects directly to Cloudflare’s APIs, without a VeDock server in between.
YOUR WINDOWS DEVICE
VeDockLOCAL WORKSPACE
CredentialsCacheJob history
YOUR ACCOUNT
Cloudflare
D1 · R2 · Workers
WHEN THE NETWORK GETS IN THE WAYUncertain is a state.
Uncertain is a state.
Not a reason to repeat a write.
Interrupted work needs context. Jobs records progress; uncertain outcomes are reconciled before another write is attempted. You stay involved when a decision is needed.
What is VeDock?
VeDock is a Windows desktop workspace for Cloudflare D1 databases, R2 storage, and Workers logs. It brings common development and maintenance tasks into one app.
Can I download it today?
Not yet. VeDock is in development and has not been publicly released. The walkthroughs on this page illustrate the product with sample data.
Which operating systems is it for?
VeDock is being built for Windows 10 and Windows 11 on x64. It is a desktop application, not a browser extension.
Do I need a Cloudflare account?
Yes. VeDock works with resources in your own Cloudflare account. Cloudflare’s service availability, permissions, retention, and usage rules still apply.
How do I connect my account?
You sign in through Cloudflare OAuth and choose the modules and access levels you need. You do not paste an API token into VeDock.
Where does VeDock store my information?
Credentials, cache, query history, and job records are stored locally on your device. API requests go directly to Cloudflare. Viewed log events stay in memory; VeDock does not create a local log archive.
What happens before a change is written?
Table edits are staged for review. R2 overwrites require an explicit choice, and deletion goes through scope, scan, preflight, and confirmation. An uncertain result is reconciled before retrying the write.
Does History use the same access as Live logs?
No. History needs the separate Workers Observability permission that Cloudflare calls Write, even though the feature is used to view logs. Live logs uses its own permission. You choose what to authorize.
WORK IN PROGRESSWINDOWS DESKTOP
Let’s build a
better workspace.
VeDock is in development and not yet released.
There is no public download yet. Have an idea
or something you’d like to discuss? We’d love to hear it.