jointops.dev valid
hitlimit
High-performance rate limiting for Node.js and Bun. Sub-millisecond latency,
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-26T01:02:48.220Z. Cached copy · Source on jointops.dev
# hitlimit
> High-performance rate limiting for Node.js and Bun. Sub-millisecond latency,
> 8 storage backends, 8 framework adapters, built-in SaaS tier support.
> Created by JointOps. MIT licensed. Zero dependencies.
## Key Facts
- 4.8M ops/sec peak (Node.js), 12.3M ops/sec peak (Bun) with memory store
- 3.16M ops/sec at 10K unique IPs — over 4x faster than express-rate-limit
- 8 stores: Memory, SQLite, Redis, Valkey, DragonflyDB, Postgres, MongoDB, MySQL
- 8 adapters: Express, Fastify, Hono, NestJS, Node.js HTTP, Bun.serve, Elysia, Hono (Bun)
- Human-readable time windows ('1h' not 3600000)
- Built-in Free/Pro/Enterprise tier support
- npm: @joint-ops/hitlimit (Node.js), @joint-ops/hitlimit-bun (Bun)
## Quick Start
- [Installation](https://hitlimit.jointops.dev/docs/installation/): Install via npm or bun
- [Quick Start Guide](https://hitlimit.jointops.dev/docs/quick-start/): Get started in 2 minutes
- [Configuration Options](https://hitlimit.jointops.dev/docs/configuration/options/): All configuration options
## Core Concepts
- [Tiered Rate Limiting](https://hitlimit.jointops.dev/docs/configuration/tiered/): Built-in SaaS tier support
- [Time Windows](https://hitlimit.jointops.dev/docs/configuration/window/): Human-readable durations
- [Custom Keys](https://hitlimit.jointops.dev/docs/configuration/custom-key/): Identify users by IP, API key, etc.
- [Skip Conditions](https://hitlimit.jointops.dev/docs/configuration/skip/): Bypass rate limiting conditionally
- [Custom Responses](https://hitlimit.jointops.dev/docs/configuration/custom-response/): Customize 429 responses
- [Response Headers](https://hitlimit.jointops.dev/docs/configuration/headers/): Rate limit headers
## Storage Backends
- [Stores Overview](https://hitlimit.jointops.dev/docs/stores/overview/): Choosing the right store
- [Memory Store](https://hitlimit.jointops.dev/docs/stores/memory/): Default in-memory store (3.16M ops/sec at scale)
- [SQLite Store](https://hitlimit.jointops.dev/docs/stores/sqlite/): Persistent storage (352K ops/sec)
- [Redis Store](https://hitlimit.jointops.dev/docs/stores/redis/): Distributed rate limiting (6.7K ops/sec)
- [Valkey Store](https://hitlimit.jointops.dev/docs/stores/valkey/): Valkey (open-source Redis alternative) distributed rate limiting
- [DragonflyDB Store](https://hitlimit.jointops.dev/docs/stores/dragonfly/): DragonflyDB high-throughput distributed rate limiting
- [Postgres Store](https://hitlimit.jointops.dev/docs/stores/postgres/): Distributed SQL store (3.0K ops/sec)
- [MongoDB Store](https://hitlimit.jointops.dev/docs/stores/mongodb/): Distributed NoSQL store for MEAN/MERN stacks
- [MySQL Store](https://hitlimit.jointops.dev/docs/stores/mysql/): Distributed SQL store for LAMP stacks / MariaDB
- [Custom Store](https://hitlimit.jointops.dev/docs/stores/custom/): Build your own store
## Framework Adapters (Node.js)
- [Express](https://hitlimit.jointops.dev/docs/adapters/express/): Express.js middleware
- [Fastify](https://hitlimit.join
…
Machine-readable: GET /v1/resolve?q=jointops.dev · GET /v1/domain/jointops.dev · this page as Accept: application/json or text/markdown · MCP lookup_domain
Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.
Own or manage this website?
If you own or manage jointops.dev, you can update its listing and review file health, discovery activity and score history.
Manage this listing — optional
What verification unlocks
See how your site is discovered—and control what agents see.
- See your website in the map
Review your indexed topics, nearby publishers sharing headings, measured listing exposure and map snapshots in a private report for your website.
- Control what agents see
Edit your listing description, tags, public contact details and additional llms.txt paths. Publish your terms for automated access, attribution and pricing.
- Make your profile eligible for search
A valid, listed, unblocked, verified profile can appear in our publisher sitemap and become eligible for search-engine visibility. Search engines decide what to index and rank.
- Appear in our llms-full.txt
Eligible verified publishers are listed by name, with their file links and summaries, in the service overview agents can read.
Free. No account registration, backlink or payment required. Public discovery remains available without verification.
Let your coding agent verify it
If your coding agent is authorized to manage this website, paste these instructions into it.
Claim my listing on Agent Web Map for jointops.dev:
1. POST https://agentwebmap.com/v1/sites/jointops.dev/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://jointops.dev/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/jointops.dev/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/jointops.dev).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verifyCorrections or removal requests: contact the directory.