Custom Obsidian plugin development at public prices
One independent developer offers a custom Obsidian plugin, a service integration, a fix for an abandoned plugin or an MCP server. A new plugin starts at $3,500, and you get a written scope, the tests and the source code.
prices from $900 · delivery from 5 working days
This work is for companies and professionals, not for consumers.
AI agents write and test my code. I set the rules and approve each release. These facts come from my release logs of 21 and 22 October 2026.
On 21 and 22 October 2026, I released new versions of 114 Obsidian plugins in about 24 hours. All 114 passed the Obsidian directory review, and 4 of them needed a second release after a failure in the review scanner.
Each release passed a build and end-to-end tests in the real Obsidian app on Linux CI, on Obsidian 1.13.4 and 1.14.4. Each release also needed a score of 85 or more in an independent review.
Tests in the real app caught two bugs that unit tests passed. One was a blank tab in Obsidian 1.14.4, and one was a race that could overwrite the sync records of a plugin. Both bugs got a fix before release, and I held back 2 plugins until their fix shipped.
On 22 October, 5 features shipped on the same day, each with CI and review. Each one answers a forum request with 41 to 299 likes. One feature failed review two times and shipped only after it restored files byte for byte.
Your plugin goes through the same process. It must pass tests in the real Obsidian app and an independent review before I release it to you.
What you can order
A price with the word from is the lowest price for that type of work. The written quote gives the final price before you pay. You do not need to select a type of work. Write what you need, and the first answer names the type and the price range.
A Custom plugin for your team, plus a private repository, a handover and 12 months of the care plan.
For a company that wants one order for the build, the install steps for each vault and a year of upkeep.
includes
All of Custom plugin, and the quote states the added price for a sync
A private repository with the source code
Written install and update steps for the vaults of your team
A handover session with your team
12 months of the care plan from acceptance, which costs $450 a month alone
not included
A listing in the public directory
A review by Obsidian, which reviews only plugins in its directory
The time starts on the day the first invoice is paid. An add-on and a larger scope add time.
Add to an order
Each add-on has one price.
Care plan$450a month
The plan covers the work after an Obsidian update breaks the plugin or the server, defect fixes and small changes. The written quote sets the size of a small change. The plan has no fixed response time, and you can stop it at the end of a month.included in Private team plugin
Directory release$1,200once
The developer submits your plugin to the Obsidian community directory and does the work in each review round. Obsidian decides, so no listing is guaranteed. For a fork, Obsidian asks for the public consent of the first author, or for 6 months with no update plus 30 days. The developer's own 116 plugins passed the automated review.
Paid tier$1,500once
A free tier and a paid tier in your plugin, with the GitHub Sponsors sign in check of the Pro tier of this site. You need your own GitHub Sponsors account, and each user needs a GitHub account. No test of that check made a real payment. A paid plugin in the public directory must state the payment, the account and the network use in its README.
Estimate your price
Select one type of work and the add-ons you need.
one time
Select a type of workfrom
each month
first payment, 50%
delivery
The estimate adds the listed price of each item, and tax is not in it. A price with the word from is a lowest price. The written quote is the price.
Write what the plugin must do, in a few lines or with the brief template. Send it to the address on this page.
Get the written quote
The first answer comes within 2 working days. The written quote states the scope, the acceptance tests, the price and the delivery time, as in a sample scope. The quote is free, and you owe nothing until you accept it. The quote needs your tax number, and it states the tax number of the seller.
Pay the first invoice
The first invoice is 50% of the price. The delivery time starts on the day the first invoice is paid.
Test the build
You get the plugin and its acceptance tests. You test it in your vault and on your devices for up to 10 working days. If you report no defect in that time, the build counts as accepted.
Accept and pay the second invoice
After acceptance you get the source code and the second invoice.
Use the 30 days of fixes
The 30 days start on the day of acceptance. Report behavior that does not agree with the scope, and the fix is part of the price.
Send a request
Write what you need in a few lines, or use the template. Send no password, no API key and no personal data of other people.
What the plugin must do:
The plugin or the service that the work starts from, if any:
Number of people, and their devices (Windows, macOS, Linux, iOS, Android):
Private plugin or public release:
Date you need it:
Company name and country:
You get an answer within 2 working days. The answer says if the work is possible, names the type of work and the price range, and asks the open questions.
Terms in short
Scope
The written scope lists each function and its acceptance test. Work outside the scope gets a new quote. The developer can decline a request.
Payment
You pay by invoice. The first invoice is 50% of the price, and you pay it before the work starts. The second invoice follows acceptance.
Failed build
A build that does not pass the acceptance tests gets fixes. If no build passes the acceptance tests 20 working days after the end of the delivery time, you can cancel the order. The developer then returns the first payment within 10 working days.
Code
You get the full source code and the build files. A private plugin has no public release, and the developer transfers to you all rights that the developer has in its new code. The transfer takes effect when you pay the second invoice. Shared parts and open source parts stay under their own licenses, and the written scope lists them.
Fixes
Each order includes 30 days of fixes, from the day of acceptance. The fixes cover behavior that does not agree with the written scope.
Obsidian updates
The plugin targets the public plugin API at the Obsidian version that the scope names. After the 30 days, the care plan covers the work when an Obsidian update breaks the plugin. Without the plan, that work gets a quote.
Confidentiality
The developer keeps your brief confidential and names no client without written consent. If you ask, the developer signs a non-disclosure agreement that permits the mail services and the AI services in use. AI services process the brief and the code, and the developer names each service before you send the brief, if you ask. Send no password, no API key and no personal data of other people.
License
The Obsidian directory asks for a license file, and it decides on closed source case by case. So plan an open license for a public plugin. A private plugin with new code only needs no open license.
Limits of this work
The tests run in the Obsidian desktop app on macOS and Linux. No test runs on Windows, on a phone or on a tablet. The written scope names your devices. You test the build on them, and behavior there that does not agree with the scope gets a fix before acceptance.
A test of a third-party service runs against a stand-in, unless you give a test account.
New plugin code in an order uses the public plugin API only, and it reads no undocumented part of Obsidian. Five plugins of this site read undocumented parts of Obsidian today, and a feature order adds no such code.
AI agents write and test the code, and one developer sets the scope, approves each release and answers for it. No team is behind this work. So each order ends with the full source code, which any developer can continue.
This service is new and has no client yet. The proof on this page is the developer's own 116 plugins, which had their first release in October 2026.
This site has no example of a plugin rescue or of an MCP server for an Obsidian vault yet.
A new plugin starts at $3,500, and one function in a plugin of this site costs $900. A price with the word from is the lowest price of that type of work. The written quote gives the final price before you pay.
Who builds the plugin?
AI agents write and test the code. One developer sets the scope, approves each release and answers for it. The price pays for a result that passes the acceptance tests in the written scope, not for hours. No team is behind this work.
What happens if the build does not pass the acceptance tests?
You do not accept the build, and no second invoice follows. The developer fixes the build. If no build passes 20 working days after the end of the delivery time, you can cancel, and the developer returns the first payment.
Who keeps the plugin working after an Obsidian update?
Each order includes 30 days of fixes. After that, the care plan covers the work when an Obsidian update breaks the plugin. Without the plan, that work gets a quote, and you have the source code for any developer.
Can the plugin connect to an internal system?
Yes, when the system has a documented API that Obsidian can reach from your devices. Four plugins of this site talk to online services through their APIs, for example Mobile Timer for Toggl Track. The tests use a stand-in for the service, unless you give a test account.
Who owns the code, and can the plugin stay private?
A private plugin has no public release, and the developer transfers to you all rights that the developer has in its new code. A private plugin arrives as files for the folder .obsidian/plugins of each vault, and Obsidian does not review it. A plugin for the public directory needs a license file, and the directory decides on closed source case by case.
Where does the data go?
A custom plugin has no telemetry, and it contacts only the hosts that the written scope names. A check of the built code stops a release that names another host. The developer needs no access to your vault, because the tests run on a sample vault.
Why pay for an Obsidian MCP server when free servers exist?
Free MCP servers for Obsidian exist, and one of them can be enough for you. This work builds a server with your list of permitted folders and actions and a log of each call. The server runs on your hardware and gives note text only to the AI client that you connect. The AI client that you connect sends the notes it reads to its model, so you select that client and that model.
Who is the seller on the invoice?
The seller is the developer of this site. The written quote and each invoice state the legal name, the address and the tax number. You get these details before you pay.
What do I send for a fix of an abandoned plugin?
Send the name of the plugin and the defect that you see. The developer reads the old code and its license before the quote, at no charge. The quote names the defects, one final price and the delivery date. It also says if the result is a fork or a new plugin.
Source: NoteMods / ToolRoutine AI services
Selected offer: Custom AI plugin
Starting price: US$5,000 per project; final quote required
The task and result you need:
Your AI client and existing tools:
The connection and data formats involved:
Number of people and access needs:
Budget range and preferred timeline:
Company name and country:
Workflow suite
From US$15,000 / project
A set of tools that works across a complete routine.
Source: NoteMods / ToolRoutine AI services
Selected offer: Workflow suite
Starting price: US$15,000 per project; final quote required
The task and result you need:
Your AI client and existing tools:
The connection and data formats involved:
Number of people and access needs:
Budget range and preferred timeline:
Company name and country:
Private team rollout
From US$30,000 / project
A custom tool suite prepared for use by your team.
Source: NoteMods / ToolRoutine AI services
Selected offer: Private team rollout
Starting price: US$30,000 per project; final quote required
The task and result you need:
Your AI client and existing tools:
The connection and data formats involved:
Number of people and access needs:
Budget range and preferred timeline:
Company name and country:
These are starting prices in US dollars for a project, separate from Pro sponsorship and the Obsidian offers above.
AI projects use a separate written quote. Scope, final price, delivery dates, ownership and support are agreed before work starts.
Hosting and other service costs are quoted separately. This site takes no project payments.
Platform approval, sales and delivery dates are not guaranteed.
The Obsidian project terms above apply to those Obsidian offers. Your AI project follows its separate written agreement.
Each button opens a prefilled email draft. You review and send it in your mail app; opening it sends nothing.
No mail app? Copy a brief and use the email address above. Send no passwords, API keys or personal data of other people.