The database, the job, the server, the log path, who to ask and what was worked out, recorded against the ticket that needed them. So it doesn't leave when your developer does.
30 days free, then $29 once. Windows 10 and 11. No account, no admin rights, and nothing leaves your machine.
batch-prd-04.corp.local/apps/risk/logs/eod_load_%Y%m%d.logEvery ticket depends on things nobody writes down properly. They end up in chat threads, old emails and one person's memory.
What was asked for, who has it and what state it is in. Not which view the report reads or where the job logs.
The runbook somebody wrote last year. Not the thing you worked out at 9pm while the batch was failing.
Connection details, jobs, servers, log paths, the people to ask and what you found, attached to the ticket and searchable in one box.
You've found that connection string three times this year: once in an email, once in chat, once by asking someone. DevDesk is where you put it the first time.
When a developer leaves, the tickets and the wiki stay. What goes with them is everything in between. DevDesk turns it into a handover document on the day you need one.
A system is recorded once and linked to every ticket that touches it. Change the connection details in one place and every ticket is right.
Oracle connections, views and tables, Autosys jobs, Tibco, Kafka, servers, log locations, config files. Add your own types with your own fields for whatever your company runs.
Paste the chat reply or the email answer against the ticket. Record meetings with what was decided and what you owe, so the decision outlives the call.
Access requests and changes raised on other teams, with the reference number, who must approve and how long each has gone quiet.
One box finds a job name, a hostname, a schema or a line from a note, and shows which tickets used it.
IntelliJ, VS Code, Visual Studio, git and Unix server access to start with. Edit them, or write your team's own.
Tickets grouped by sprint, with the current one marked, so this fortnight's work is the first thing you see.
DevDesk answers that from what is already recorded, with the specific gaps named.
DevDesk holds hostnames and connection details, so it is built to be easy for a security team to say yes to.
It serves its own pages to your browser on 127.0.0.1 and talks to nothing else. No account, no telemetry, no cloud sync.
Everything is in a single database file in your user folder. Back it up by copying it. Export to JSON at any time.
The installer is code-signed by BigFish consulting group and installs for the current user only. The licence is a file checked offline.
DevDesk includes an MCP server. An assistant such as Claude can look up a system in your catalog, or record a log path when you say "remember this", using an assistant your company has already approved. DevDesk itself contains no AI and sends nothing anywhere.
Try everything free for 30 days. If the trial ends, nothing is locked and your notes stay yours; exported documents carry a trial line until you buy.
Secure payment by Stripe. For several seats, change the quantity at checkout. Your licence file is emailed from sales@big-fish.net, usually within one business day.
No. It sits beside them. You type the ticket key and DevDesk keeps the working details that neither tool has a natural place for. It does not connect to Jira.
For remembering things, OneNote works. The difference shows up afterwards: DevDesk can tell you which tickets touch a database, what you have been waiting on for a week, and can produce an organised handover document, because the notes are structured.
In one database file under your Windows user folder, in .devdesk. We cannot see it or recover it. Uninstalling the program leaves that file alone.
Windows 10 or 11, 64-bit, and a browser. Nothing else to install. It does not need administrator rights.
Everything keeps working and nothing is deleted or locked. Handover documents and reports carry a line saying the copy is unlicensed until a licence file is added.
Yes. The installer is signed by BigFish Consulting Group LLC. You can confirm it under the file's Properties, on the Digital Signatures tab.
Add its systems once. The next time you need that log path, it is one search away, and so is the handover.
Version 1.0.0 · 12 MB · Windows 10 and 11, 64-bit