
Quebids
From $79 onceActively maintained
1.7k linking domains
Established
- For
- Consultants, NGOs, SMEs and government contractors finding public tenders to bid on.
- Price
- From $79 oncepricing page, read Oct 22, 2026
- Activity
- Actively maintainedsite updated 4 days ago
- Company
- since 2025per their About page
- Used for
- monitor public tenders through keyword and region alerts
- track shortlisted tenders in a bid pipeline
- draft tender proposals with AI assistance
- Launched on Product Hunt on May 10, 2026Product Hunt ↗
From $79 once
- Founded2025per their About page ↗
- Certifications they stateSOC 2 Type II · ISO 27001 · GDPR · PCI DSS · CCPAsecurity page ↗
- Privacy policy updated2026-04-28privacy policy ↗
These are Quebids's own statements, read from its pages. We did not audit them. A line that is missing was not found on the pages we read; it does not mean the practice is absent.
- API docsquebids.com/apithe vendor's page ↗
This card as JSON, for your agent →
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
Not it? Say what you need
betaThree tools from the Atlas for the job you describe, each with what fits and what does not.
No notes yet. What do you use Quebids for?
Sign in to leave a noteWhat is Quebids?
Finds public tender notices across 50 government and development sources, sends matched alerts, and tracks bids in a pipeline.
Who is Quebids for?
Consultants, NGOs, SMEs and government contractors finding public tenders to bid on.
How much does Quebids cost?
Paid plans start at $79 once, per Quebids's pricing page on 2026-10-22.
Is Quebids free?
No. Its pricing page showed no free plan on 2026-10-22.
Do people use Quebids?
Established.
Is Quebids still maintained?
Actively maintained: site updated 4 days ago.
Is Quebids safe?
We do not audit vendors. What Quebids publishes, read 2026-10-22: SOC 2 Type II, ISO 27001, GDPR, PCI DSS, CCPA stated on its security page.
How we read a tool
No votes, no reviews, no vendor claims. Every week a crawler reads each tool's own site and a few public registries, and the words on the card are bands over what it read.
- Use: visits to the site (estimated), installs from npm and PyPI, presence in Chrome's usage report.
- Activity: the newest release on GitHub, npm or PyPI; the newest dated page on the site; open roles on a public jobs board.
- Price: the vendor's own pricing page, read with the date. A figure is printed only when it is on that page.
- The line and the use cases are written by us from the homepage, one tool at a time, and refused when they repeat the vendor's marketing.
How AI assistants read each site — the reading vendors ask us about — is on each tool's own visibility page.
How we read every tool → · By INITE Atlas Desk
Cookies
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.