SearchTypesense
pcloudhosting · Software Development
Certification per Microsoft Marketplace.
Evidence tier Source Confirmed · 9 captures on record
What the publisher says
As described on Microsoft Marketplace.
Typesense is a fast, open-source search engine designed for modern applications, especially ecommerce.
It provides instant, typo-tolerant search with a simple REST API, making it ideal for building scalable and developer-friendly “headless” search solutions.
Show the rest of the publisher’s description (42 more lines)
Features of Typesense:
- Blazing-fast full-text search built in C++.
- Typo tolerance and instant search results.
- Easy-to-use RESTful API for integration.
- Multi-tenant API keys for secure access control.
- Synonyms support for better search relevance.
- Filtering, sorting, and faceting capabilities.
- Real-time indexing and updates.
- Lightweight and easy to deploy.
Usage Instruction for Typesense:
Typesense - Installation & API Commands
$ sudo su
$ sudo apt update
Configure Typesense (API Key access):
$ sudo nano /etc/typesense/typesense-server.ini
Start and enable Typesense service:
$ sudo systemctl start typesense-server
$ sudo systemctl enable typesense-server
Check service status:
$ sudo systemctl status typesense-server
$ curl http://localhost:8108/health
$ typesense-server --version
Check available collections:
$ curl http://localhost:8108/collections \
-H "X-TYPESENSE-API-KEY: YOUR_API_KEY"
Import data using connector script:
$ python3 import_data.py products.csv
Create Multi-tenant API Key:
$ curl -X POST http://localhost:8108/keys \
-H "X-TYPESENSE-API-KEY: YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"description": "tenant1",
"actions": ["documents:search"],
"collections": ["products"]
}'
Note:
- Replace YOUR_API_KEY with your actual Typesense API key.
- Ensure Typesense service is running before executing API commands.
Disclaimer: Typesense is an open-source project released under the MIT License.
It is maintained by the community and provided "as is" without any warranty, express or implied.
Users are responsible for proper configuration, security, and compliance while using Typesense.
Agent build and provenance
See the full provenance
The layer-by-layer build, the evidence behind each claim, the risk basis and the cross-marketplace links are open to any account. Some rows are disclosed, some the source leaves Unknown; a free account shows you which.
Compliance
- FedRAMPConfirmedNot listed90%, registry-checkedNo FedRAMP Marketplace entry matched this vendor's domain, checked 2026-08-27registry recordas observed 2026-08-27
Confirmed means matched to a public authoritative registry. Claimed means the vendor or its listing states it, not yet cross-checked. A framework not shown was not found in any source we hold, which is not evidence against it. Not listed means a scoped registry check found no match for this vendor's domain: a No is a scoped registry check, not a compliance judgment. Confidence bands: 95% domain-verified, 90% registry-checked, 80% self-attested, 70% weak signal. Self-attested items marked “vendor's site” are gathered from the vendor's own website and are not verified by us.
Vendor
External enrichment · as of 2026-08-29
Sources
Publisher resources
1 linkLinked repositories
Unknown means this listing does not publish a repository. It is not a statement that the code is closed, and a linked repository is not a claim that the publisher wrote it: the registry computes that relationship privately and does not publish it.
Evidence risk is the share of the build you cannot see before you deploy, not a security rating. Sign in to see the layer-by-layer basis for this band.

