No account - no file lock-in - Android + Windows

One folder. Every view. Every tool. Still your files.

Plan, write, connect ideas, test APIs, and inspect project Git in one portable workspace. Start with a normal task or note. Add technical tools only when your work needs them.

Windows: available on Microsoft Store. Android: closed testing — contact the developer to join.

  • Ordinary readable files
  • Copy or Git-clone and continue
  • Manual, review-first, or safe automation
DevDesk workspace illustration with planning and project tools
Open project.devdesk. DevDesk recognises the folder and rebuilds the local workspace.
AI-ready local projects

Better project context for your AI. Final control for you.

Connect one or more MCP-compatible agents. Every session stays pinned to its assigned workspace while DevDesk shows who is connected, what observable tool is running, and which proposal needs your review.

  • Isolated workspace sessions
  • Live privacy-safe activity
  • Token-budgeted context
  • No direct project writes
  • Conflict checks and undo
Focused project workflow
  1. Understand the project Relevant source, code structure, tests, Markdown, and graph context.
    Read only
  2. Prepare the complete change A fingerprinted multi-file proposal with optional verification choices.
    Review
  3. You decide what happens Compare every file, approve selected checks, apply safely, or undo.
    Your control

Your files remain in the workspace you own.

Why DevDesk

Your work should not be trapped inside the tool that helps you see it.

DevDesk keeps ordinary project files as the source of truth, then gives them useful views, relationships, portability, and optional specialist tools. The distinctive value is the complete combination, not a claim that every individual feature is unique.

Work your way

See the same task, note, goal, meeting, or decision as a list, table, cards, board, calendar, timeline, outline, map, or relationship.

Keep ownership

Your content stays in the folder you chose. Open it in another editor, back it up normally, and share only the files you approve.

Grow without moving

Add connected Markdown, portable Visual Canvas, JSON, OpenAPI, saved API testing, OKF checks, Diff, and workspace-scoped Git as needed.

Two simple paths

Useful for everyday work. Serious enough for a real project.

For life, study, and work

Begin with what you already understand.

Create tasks, notes, goals, assignments, meetings, decisions, sources, outlines, and drafts. DevDesk handles Markdown structure and graph connections for you.

  • Personal, Study, Business, and Research / writing starters
  • Today, Board, Calendar, Timeline, Outline, and Relationships
  • No frontmatter, JSON, node, edge, or OKF knowledge required
Choose an everyday recipe
For builders

Keep docs and tools beside the work they describe.

A project can carry portable docs, safe settings, a sanitized API workspace, OpenAPI, JSON, and knowledge links. Parent-repository Git can be detected while DevDesk actions remain restricted to the selected workspace.

  • Nested folders and exact selected-file tool context
  • Automatic portable API artifact without portable secrets
  • Clone, open project.devdesk, and continue
See the portable project workflow
Portable by design

Three steps from this device to the next.

  1. 1

    Choose or create a folder

    Preview a new workspace, or open an existing folder without writes. Add portable identity only when you choose it.

  2. 2

    Work with ordinary files

    DevDesk derives views and relationships. Safe project writes stay reviewable, bounded, and conflict-aware.

  3. 3

    Copy or clone and reopen

    Open project.devdesk. Local registration and indexes are rebuilt; protected values and trust stay device-local.

One source, not duplicate systems

A workspace that changes shape without changing ownership.

What matters Single-purpose project apps DevDesk
Source of truth Often an app-specific workspace or one specialist format Ordinary files in your selected folder
Ways to see work Usually centred on one product category Table, cards, planning views, map, graph, and Visual Canvas
Developer context Often opened in separate tools and separate workspaces API, OpenAPI, JSON, Diff, and scoped Git beside project docs
Move to another system May require export, sync, or setup recreation Copy or clone, then open project.devdesk

Different products solve different problems. This comparison describes DevDesk's design goal, not every product in each category.

Trust before automation

Helpful does not mean hidden.

Read-only indexes can rebuild automatically. Project writes use Manual, Review changes, or bounded Safe automatic mode. Secrets, cookies, execution trust, recents, and personal layout do not belong in portable project files.

No silent overwrite

Existing paths and external file changes are preserved and reported.

No portable secrets by default

Sanitized API structure can travel; protected values stay on the device.

No surprise Git scope

File actions stay inside the workspace. Local commits remain explicit and require a final staged-index review.

Complete, searchable manual

Start with a goal. Learn technical detail only when it helps.

Manual-powered support

Ask about DevDesk. Get the matching manual guidance.

The static DevDesk Support Assistant runs entirely in this website and is ready for GitHub Pages. It searches the published manual, quotes relevant guidance, and links every answer to its source page. No account, API key, or hosted AI service is used.

  • Manual onlyAnswers are extracted from published DevDesk guidance.
  • Sources includedOpen the relevant page to verify each answer.
  • Private by defaultYour question stays in the browser and is not stored.
Featured graph-to-code demo

One Markdown task. One prompt. Reviewed code.

Watch Codex follow a DevDesk knowledge graph from one task to the relevant brief, architecture, source, and tests. Then download the exact starter workspace and reproduce the review-before-write flow on your own device.

  • Task-linked graphOne Markdown entry point leads to the exact planning and architecture context.
  • Bounded code understandingThe agent inspects the relevant source and tests without an uncontrolled repository dump.
  • Approval before writeReview the complete two-file proposal, apply it recoverably, or reject it.
Keep the folder. Gain the workspace.

Start simple today. Your setup can grow with the project.

Android and Windows availability is shown transparently on the downloads page. No unreleased platform is presented as available.