Back to services
Service

Obsidian Plugin Development

Your team runs on Obsidian and it does almost everything you need. I build the part it's missing, and I have a plugin that passed Obsidian's public review.

Obsidian Plugin Development
Type
Obsidian Plugin Development
Timeline
2-6 weeks
Technologies
TypeScript, Obsidian API, CodeMirror 6, Svelte, WASM
What you get

Your team runs on Obsidian. It does almost everything you need, except the one thing that would save an hour a day. Nobody built it as a public plugin because your workflow is specific to you.

That's what I build.

I'm published, not just capable

S-Calc is my Obsidian plugin, listed in the official community marketplace. Write expressions in an s-calc code block and each line's result appears inline in your theme's accent colour, live as you type. It handles arithmetic, variables, percentages, unit conversion, live currency rates, and plain-language dates. TypeScript, mathjs, chrono-node, and CodeMirror 6, released under MIT and in public use.

Getting into that marketplace means an independent reviewer read the code and the security model and approved it. Most developers who tell you they can build an Obsidian plugin have never had one accepted anywhere. That is the difference you are paying for.

I also run Obsidian as my own daily vault, so I already know where the API is awkward. I'm not learning your tool on your budget.

What I build

Internal tooling. Your team's process, inside the vault they already live in. Nobody learns a new app.

API and data integrations. Pull your CRM, database, issue tracker, or internal service into a note so people stop alt-tabbing to a dashboard.

Custom views and editor behaviour. CodeMirror 6 work, live preview rendering, custom panels. This is the deep end of the API and it is where most plugins fall over.

Public plugins. Something you want to publish under your own name, built to survive community review the first time.

How it works

  1. A call. You show me the friction. Free, 30 minutes.
  2. Scope. What it does, what it doesn't, what it costs. In writing, before you commit.
  3. Build. You get something installable in your vault by around week two.
  4. Handover. Source, docs, and a build you can publish or keep private.

What you get

The code is yours. Documented well enough that another developer can maintain it without me, because a plugin only one person understands is a liability, not an asset.

Ready to start?

Tell me what your team keeps doing by hand. If a plugin isn't the right answer, or an existing one already covers it, I'll tell you that on the call and charge you nothing.

Reach me by email, on LinkedIn, or fill in the form on this page.

Features
  • Published in the Obsidian community marketplace (S-Calc)
  • Custom editor views and CodeMirror 6 work
  • API and external data integrations
  • Live preview and reading-mode rendering
  • Settings UI and vault-safe storage
  • Community review and submission support
  • Desktop and mobile compatibility
  • Documented handover, you own the code
Deliverables
  • Working plugin, installable and tested in your vault
  • Clean, documented TypeScript source you fully own
  • Build and release pipeline
  • Community marketplace submission support, or a private build
  • User documentation for your team
  • Handover walkthrough
Let's talk

Interested? Get a quote

Tell me about your project and I'll reply within one business day.

Published, not just capable S-Calc is listed in the official Obsidian community marketplace and passed their public code and security review. Most developers offering this have never had a plugin accepted anywhere.
I use Obsidian every day My own working vault runs on it. I already know where the API is awkward, so I am not learning your tool on your budget.
Deep API work, not surface CodeMirror 6, live preview rendering, and custom views are where most plugins break. That is the part I have already shipped.
You own it outright Full source, documentation, and build pipeline. Nothing licensed back to you, nothing dependent on me being around next year.

Request this service

By submitting, you agree to the privacy policy. I'll respond within one business day.

FAQ

About this service

Obsidian plugin projects start at $3,000. A focused internal tool that automates one workflow sits near the lower end, while a plugin with custom editor rendering, a settings interface, and community marketplace submission costs more. Scope and price are agreed in writing before you commit, and the first 30-minute call is free so we can work out whether a plugin is even the right answer.

Yes. S-Calc is listed in the official Obsidian community marketplace, released under MIT, and in active public use. It renders live calculation results inline in your notes, handling arithmetic, variables, percentages, unit conversion, live currency rates, and plain-language dates. Marketplace acceptance means an independent reviewer checked the code and security model and approved it, which is the part most freelance developers cannot show you.

Yes, that is one of the most common requests. A plugin can call your CRM, database, issue tracker, or internal API and render the result directly in a note, so your team stops switching to a dashboard to read numbers. The work involves handling authentication safely, caching sensibly so the vault stays fast, and failing gracefully when the network is unavailable.

It can, and this is worth deciding early because it shapes the build. Obsidian mobile does not support Node APIs or filesystem access the way desktop does, so a plugin that shells out to local tools is desktop-only by nature. If mobile matters to your team, say so during scoping and the plugin gets architected for it from the start rather than retrofitted.

You own it completely, and it is your choice whether it is published or private. You receive the full TypeScript source, documentation, and the build pipeline, with nothing licensed back to you. Many teams keep their plugin internal because it encodes their own workflow, and installing a private plugin in a vault is straightforward. If you do want it public, I handle the community review submission.

Often yes, sometimes no. If your team repeats a manual step several times a day, a plugin usually pays for itself quickly because it removes the step instead of documenting it. But Obsidian has a large community plugin ecosystem, and if something already covers your need I will point you at it and charge you nothing. The free call exists to find out which of those two situations you are in.