An end-to-end tour: signing in, extracting your first product, finding alternative suppliers, and running an automated procurement pipeline. No prior setup knowledge assumed.
Sidrun Source is an AI assistant for procurement and sourcing teams. It does two main jobs:
Sourcing β give it a product (a URL, a PDF spec sheet), and it finds equivalent products from other suppliers, compares specs against dealbreaker attributes, and shows a scored, explained match for each.
Procurement Pipeline β give it a purchasing need in plain language, and a team of agents handles vendor selection, quote requests, quote comparison, PO creation, and approval routing.
Both flows are accessible from the top navigation bar after you sign in. There's also an in-app feedback widget on every page for quick notes, and a dedicated Feedback page for feature requests.
Your first 10 minutes
Go to https://source.sidrun.ai/ui/login.html.
Click Continue with Google (or sign up with email).
You land on the Sourcing workspace.
Click + New and paste a supplier product URL. Sidrun extracts the product into a structured baseline.
Click Find alternatives β Sidrun searches other vendors and ranks candidates by spec match.
Open Pipeline in the top nav to see the procurement agent workflow.
Type a need (e.g. "I need 50 boxes of nitrile gloves, size M, by next Friday") and watch the agents execute.
That's the whole loop. The rest of this guide explains each piece in depth.
Signing in
Sidrun Source uses Supabase Auth. You can sign in with:
Google β one click, fastest.
Email + password β click Sign up on the login page, set a password (min 8 chars), and confirm via the email Supabase sends you.
After signing in you are redirected to /ui/sourcing.html. The session lasts about an hour and is refreshed automatically while you're using the app. Click Sign out in the top-right user chip to end the session.
source.sidrun.ai/ui/login.html
Figure 1. The login screen β pick Google or email.
Trouble signing in?
The Google screen shows an unfamiliar domain. That's the Supabase project URL. Until OAuth verification is finalized, this is expected.
The app at a glance
The top bar has two sections:
Figure 2. The top app bar β navigation on the left, your user chip on the right.
Run the multi-agent procurement workflow on a plain-language need.
Feedback
A dedicated feature-request page β post ideas, vote, and comment on other requests.
Help
Links back to this guide.
Admins additionally see Analytics, Errors, and Admin links.
To the right of the nav, a language toggle (EN/ET) and a settings gear (β) sit next to your user chip. Your name and organization appear in the chip itself; click Sign out inside it to end the session.
Sourcing workspace
The Sourcing page is split into three columns:
Left β history of products you've extracted previously. Click any row to reopen it.
Centre β the active product (the "baseline") with all extracted attributes, documents, and price.
Right β alternative candidates from other vendors once you run a search.
Figure 3. The three-column Sourcing workspace: history on the left, the baseline product (with spec grid and attached datasheet) in the middle, and ranked alternatives on the right with match confidence, source URLs, and one-click actions to Exclude vendor or Send to Pipeline.
Step 1 β Extract a product
Click + New to open the Extract a new product dialog. You have 3 ways to bring a product in:
Paste a URL. Paste a supplier product URL and hit Extract. Sidrun fetches the page, parses the product, and saves it as the baseline. No URL handy? A few example product links are offered as quick-fill chips.
Upload a PDF spec sheet. Drop a datasheet PDF onto the upload zone in the same dialog. Useful when the supplier doesn't have a public product page.
Use the bookmarklet. Behind the "Can't fetch the page? Install the Sidrun bookmarklet β" link, drag the "π Sidrun Source" button to your browser's bookmarks bar. Then, on any supplier page, click the bookmark and the page is sent to Sidrun for extraction.
Some supplier sites block automated fetches. If that happens, the dialog shows a "This supplier blocked our fetch" notice pointing you to the bookmarklet, with a "Continue with basic details anyway" option if you'd rather not install it.
The extractor pulls out: product name, manufacturer, catalog number, price, pack size, key spec attributes, document links (datasheets, MSDS, manuals), and an image. If anything looks off, you can edit the baseline before searching.
Figure 4. The Extract dialog β URL, PDF upload, and a bookmarklet shortcut.
Step 2 β Dealbreaker specs
Some specs matter more than others. Sidrun automatically identifies dealbreaker attributes for your product's category β the values that must match for a candidate to be acceptable (e.g. package size, concentration, certification grade, voltage) β as part of running Find Alternatives. These aren't something you click to set; they come from the search itself.
Dealbreakers are what you see in the spec-diff view when you compare candidates, so you can see at a glance whether an alternative actually fits.
Step 3 β Find alternatives
Click Find alternatives. Sidrun:
Submits searches to multiple supplier search endpoints.
Waits for responses (some vendor sites rate-limit, so this can take 30β90 seconds).
Opens likely product links and extracts structured data from each.
Scores each candidate against your baseline and dealbreakers.
A progress strip shows which phase the search is in. When it finishes, candidates appear in the right column ranked by match quality.
Step 4 β Compare and act
Click any candidate to expand it:
Spec diff table highlights matches (green), mismatches (amber), and missing data (grey).
Documents β links to any datasheets, MSDS, or manuals found on the candidate's page.
Price β shown in the candidate's native currency where available.
Click the match-score badge for a "Why this result?" breakdown β how much of the score came from product-name similarity, attribute match, pack fit, document availability, and vendor relevance. You can also rate a candidate with the π/π control on its card, open the source page, mark a vendor Exclude vendor to drop it from future searches (excluded vendors are listed above the candidates, with a Clear all to reset), or click Send to Pipeline to hand it to the procurement workflow. Sourcing records persist β you can come back to them any time from the History sidebar.
Figure 5. Spec diff β green matches, amber mismatches, grey for missing data. β marks a dealbreaker.
Procurement Pipeline
The Pipeline page (/ui/pipeline.html) runs an automated multi-agent procurement workflow. Each agent is a specialised step; together they take a request from "I need X" to a submitted purchase order.
The stages
The flow has eight stages, shown as connected nodes on the canvas. Each node lights up blue while running, green when complete, amber when paused, red on error:
Figure 6. The pipeline canvas β eight stages laid out in a snaking flow. The Agent Inbox node pauses the run until a vendor's reply is pasted in, then hands off to Quote Comparison. Each node carries a status pill and a context chip. Green border = complete, amber = paused, grey = not yet reached.
Stage
What it does
π Need Detection
Parses your request into a structured purchasing need (item, quantity, unit, category, deadline, budget).
πͺ Vendor Selection
Searches your approved-vendor list, scores each, and shortlists the best fits.
π Quote Request
Generates an RFQ document and emails it to the shortlisted vendors.
π¬ Agent Inbox
Pauses and waits for a human to paste in each vendor's reply β inbound replies aren't read automatically.
βοΈ Quote Comparison
Parses the pasted quote replies and picks the best-value option.
π PO Creation
Builds the purchase order and submits it to the ERP.
β Approval Routing
If the PO exceeds your approval threshold, the run pauses here and notifies an approver.
π¦ Order Tracking
After PO submission, polls delivery status until the order arrives.
Running your first pipeline
On the Pipeline page, type a request in plain language. Examples:
"Need 50 boxes of size-M nitrile gloves for the Tartu lab, budget β¬400."
Click Start run. The Need Detection node lights up first.
As each agent finishes, the next node activates. Click a node at any time to open its Skills panel β the tools, model, and inputs/outputs it used, editable if you need to adjust its configuration.
At Agent Inbox, the run pauses: open the outbound RFQ email and paste each vendor's reply into the reply box to continue.
If the run pauses at Approval Routing, an email is sent to the assigned approver with an approval link, and the request also shows up in-app for review/approval. The pipeline resumes automatically once it's decided.
What you'll see in the UI while it runs
The canvas β animated edges flow between nodes that are talking to each other.
The inbox β the Agent Inbox node shows outbound RFQ emails and is where you paste vendor replies back in.
The audit timeline β chronological log of every event: need detected, vendors scored, RFQ generated, etc. Useful for auditing or compliance.
Privacy & data
Your sourcing records, pipeline runs, and uploaded documents are stored in your organization's Sidrun project and nobody else outside has access.
Other users in your organization can see your records if they're given access; users outside cannot.
You can delete any record from its row in the History list β it's removed from your History and from other users' view immediately.
Getting help
In-app feedback widget β click the feedback widget (right-side yellow bar on every page), take a screenshot and send a note.
Feedback page β the Feedback link in the top nav opens a dedicated page where you can post feature requests, vote, and comment on other people's.
Stuck on sign-in or a broken page β note the URL and the error message, then send it via the feedback widget.