Start with Core. Add Pro when your workflow needs more.

Smart Plugins is built around a simple public rule:
Start with Core and get one useful result from your own notes. Add Pro when you need more context, faster retrieval, model routing, generation, cleanup, graph, or approved action.

This is the public product boundary.
It keeps the first step easy to trust and makes the advanced path easier to choose.

If you are new, Core gives you the shortest path to first value.
If your workflow is already compounding, Pro gives you the deeper lane for a specific need.

Explore Pro plugins
Explore Core plugins

Already want to see the flagship workflow? Start with Smart Connections.

The real problem is not more AI

Most people do not need more AI features.
They need better workflows around AI.

Inside Obsidian, the repeat problems are familiar:

• "I know I wrote this somewhere, but I cannot find it in flow."
• "I can get a good answer, but only if I gather the right notes first."
• "I keep rebuilding the same context and the same prompt structure."
• "My chats drift away from the work they were supposed to support."
• "Repeated notes and fragments keep creating rework."
• "Advanced AI tools sound powerful, but they often make my system harder to trust."

Those are workflow problems.
Not model problems.

That distinction matters because models will keep getting better.
As they do, the workflow layer becomes more important, not less. Better models make bad context, weak continuity, scattered structure, repeated source material, and brittle action-taking more expensive.

Smart Plugins is built for that layer.
Not as a giant pile of AI features for Obsidian, but as a trusted, local-first workflow layer between your notes and increasingly capable AI.

Why Core stays simple

Core gives you the shortest path to one useful result from your own notes.

In practice, that means something concrete:
you should be able to install a Core plugin, open one real note, and see a result you can verify.
No provider maze. No giant settings surface. No long decision tree before first success.

Core should feel calm.
Core should feel obvious.
Core should make you think, "Yes, this helps," before it ever asks you to think about advanced control.

That is why the Core plugins focus on the essential jobs:

• Smart Connections helps you rediscover relevant notes and search by meaning.
• Smart Context helps you gather the right notes, blocks, folders, and links into grounded context.
• Smart Templates helps you apply trusted structure to that context.
• Smart Chat keeps conversations anchored to notes instead of letting them disappear into tab history.

Each one is built to solve a clear moment well.
Not every possible moment.

That restraint is a feature.
A smaller Core is easier to learn, easier to explain, easier to document, and easier to trust.
That matters for local-first tools, where people are not just evaluating utility. They are deciding what they can rely on.

Why Pro goes deeper

Pro exists for workflows that have already moved past the first useful path.

You do not need Pro to get one useful result from Smart Plugins. Use Core first when you want the fastest way to see related notes, build context, structure a prompt, or keep a thread attached to a note.

Use Pro when a real workflow needs more:

• closer-to-the-work retrieval surfaces
• advanced ranking, filtering, and large-vault support
• external files, media, repos, and richer context
• local/API model routing
• in-Obsidian generation and review
• duplicate or near-duplicate cleanup
• graph and landscape views
• approved action inside the vault

Many products make the same mistake here: they put every advanced idea into the main product because it looks impressive in a feature list.

The result is predictable. The product gets harder to learn. Docs rot faster. Support gets harder. The first-run experience gets worse for everyone.

Smart Plugins takes a different path.

Core stays simple so the first useful workflow remains easy to trust.
Pro goes deeper when the workflow has already earned more control.

That is what Pro is for.

Connections Core includes sidebar and footer workflows for related notes.
Connections Pro adds granular inline discovery, graph/list exploration, Bases workflows, ranking, filtering, custom algorithms, and large-vault performance.

Context Pro extends context beyond plain notes into images, PDFs, repos, external files, Bases, and tighter control surfaces when the assignment needs that evidence.

Chat Pro adds local and cloud model routing, stronger per-thread control, history/search, and deeper retrieval-native workflows.

Templates API Extension Pro keeps generation and review inside Obsidian with configured models.

Smart Graph gives you a landscape view when list results feel too flat.

Smart Dedupe helps review duplicate and near-duplicate blocks before they become repeated work or repeated context.

Connect Pro turns chat into approved vault actions you can review.

This is not a random bag of extras.
It is the advanced workflow lane.

Why Smart Environment matters

There is a third layer that matters just as much, even if it is less visible day to day: Smart Environment.

Set sources, models, and exclusions once.
Smart Plugins reuse them.

Why does that matter to users?
Because repeated setup is a hidden tax.
If every plugin asks for the same sources, models, exclusions, provider settings, and status checks separately, the whole suite becomes less coherent and more fragile.

Smart Environment keeps those shared pieces in one place so Connections, Lookup, Context, Chat, Templates, Graph, Dedupe, and other Smart Plugins can reuse the same setup instead of rebuilding boundaries from scratch.

Not all value is visible in a screenshot.
Some of the deepest value is that the suite gets easier to trust as it grows.

Why this structure makes the product better

Separating Core and Pro makes the product better for both kinds of users.

Core stays simple.
The free path is easier to install, easier to understand, and faster to trust. It focuses on the workflows that should just work.

Advanced workflows stay maintainable.
Pro is where deeper integrations, experiments, and high-change features can evolve without making Core harder to learn or more fragile to maintain.

The whole suite gets stronger over time.
Both Core and Pro run on the same Smart Environment foundation, so improvements to shared infrastructure benefit the entire ecosystem.

How this shows up across the suite

This philosophy is not abstract. It already shapes how the suite works.

Smart Connections

Start here when the first useful question is:
What in my notes matters right now?

Core gives you related notes, footer workflows, and search by meaning.
Pro brings more connection opportunities and deeper control through inline discovery, graph/list exploration, Bases workflows, ranking, filtering, custom algorithms, and large-vault performance.

Smart Context

Use it when grounded AI is the real bottleneck.

Core gives you a fast way to assemble notes, blocks, folders, and linked context.
Pro extends that workflow into images, PDFs, repos, external files, Bases, and other advanced inputs when the real-world source of truth goes beyond plain notes.

Smart Templates

Use it when the problem is not just context, but structure.

Core helps you apply reusable Markdown templates to the work already in front of you.
Pro keeps generation and review inside Obsidian when you want the full loop to stay inside your vault workflow.

Smart Chat

Use it when continuity matters.

Core keeps threads anchored to notes so conversations do not disappear into browser history.
Pro adds model routing, stronger thread-level control, history/search, and deeper retrieval-aware workflows.

Smart Graph

Use it when lists feel too flat.

Graph shows clusters, neighborhoods, and nearby context so you can select a visual region and turn it into a next action.

Smart Dedupe

Use it when repeated work or repeated context starts costing attention.

Dedupe is review-first. It surfaces likely repeated blocks or notes so you can compare, preserve useful neighbors, and clean up only after the overlap is clear.

Connect Pro

This is the action layer.
Not the front door.

It becomes valuable after trust already exists, when you want chat to move from suggestion into approved action inside the vault.

Explore the plugin suite
See Smart Context

Choose your lane

You do not need everything on day one.
The suite is designed so you can choose the lane that matches where you are right now.

Start with Core

Best if you want to install a plugin, feel value quickly, and build trust in the workflow before adding complexity.

Start free with Core

Go deeper with Pro

Best if a Core workflow already proved useful and you now need one specific layer of depth: closer-to-the-work retrieval, richer context, model routing, in-Obsidian generation, cleanup, graph, approved action, or large-vault support.

Start with one Pro workflow

Why this roadmap compounds

This approach leads to a different kind of roadmap.
It does not optimize for the most features.
It optimizes for the most durable workflow value.

That means Smart Connections remains the flagship wedge because the first useful question is still, "What in my notes matters right now?"
It means Smart Context remains central because grounded AI is mostly about context quality.
It means Smart Templates matters more over time, not less, because structure becomes more valuable as models become more capable.
It means Smart Chat is not just about chatting; it is about continuity.
It means Smart Graph matters when lists cannot show the shape of the topic.
It means Dedupe matters when repeated material makes AI harder to review.
And it means action-taking belongs after trust, not before it.

In other words, the suite is designed to compound.

A better product shape for the long run

Core helps you start safely.
Pro adds advanced workflows when your work needs more control.
Smart Environment ties the suite together so the whole system gets stronger instead of messier.

That is the philosophy.
Not because it sounds tidy.
Because it produces better software.

The goal is not to build the loudest AI toolkit in Obsidian.
The goal is to build the one that keeps getting more useful as the market gets noisier.

Explore Pro plugins
Start free with Core

Want the longer explanation? Read Introducing Pro plugins.