dynoxide.dev valid
Dynoxide
Dynoxide is a DynamoDB emulator written in Rust and backed by SQLite, verified against real AWS by a public conformance suite. One emulator runs as a local HTTP server (a drop-in for DynamoDB Local), as an in-process library for Rust and iOS, as a WebAssembly build for the browser, and as an MCP server for coding agents. It is a single static binary that starts in about 2ms and downloads at about 3 MB, with no runtime or database to install.
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-27T09:51:49.850Z. Cached copy · Source on dynoxide.dev
# Dynoxide
> Dynoxide is a DynamoDB emulator written in Rust and backed by SQLite, verified against real AWS by a public conformance suite. One emulator runs as a local HTTP server (a drop-in for DynamoDB Local), as an in-process library for Rust and iOS, as a WebAssembly build for the browser, and as an MCP server for coding agents. It is a single static binary that starts in about 2ms and downloads at about 3 MB, with no runtime or database to install.
Conformance: grade A on the independent paritysuite.org suite, diverging on 2.0% of 1678 tests and covering 99.2% of them, scored against v1.5.0 on 2026-10-25. Latest release: v1.5.0 (product; the crates.io crate dynoxide-rs is versioned separately at 3.2.0). Licence: MIT OR Apache-2.0.
## Documentation
- [Quick start](https://dynoxide.dev/docs/quick-start): From zero to a running DynamoDB endpoint with data in it, in four commands.
- [Installation](https://dynoxide.dev/docs/installation): Install via npm, Homebrew, Cargo, Docker, pre-built binaries, or GitHub Actions.
- [CLI reference](https://dynoxide.dev/docs/cli): Every command and flag for the native binary.
- [MCP server](https://dynoxide.dev/docs/mcp): The built-in MCP server, its tools, and setup for Claude Code and Cursor.
- [Embedded SDK](https://dynoxide.dev/docs/sdk): Use Dynoxide as a Rust library, in-process, with no network overhead.
- [Browser (WASM)](https://dynoxide.dev/docs/browser): Run the emulator in the browser via WebAssembly and OPFS.
- [PartiQL](https://dynoxide.dev/docs/partiql): The supported PartiQL grammar, the RETURNING clause, and where it differs from the classic API.
- [Streams](https://dynoxide.dev/docs/streams): Enabling and reading DynamoDB Streams, and the single-shard model to test around.
- [Import](https://dynoxide.dev/docs/import): Load a DynamoDB Export locally, with rule-based anonymisation of production data.
- [Compatibility](https://dynoxide.dev/docs/compatibility): What Dynoxide implements, what it deliberately does not, and the behavioural differences.
- [Configuration](https://dynoxide.dev/docs/configuration): Ports, persistence, encryption, and the other runtime options.
- [Conformance](https://dynoxide.dev/docs/conformance): How Dynoxide is scored against real DynamoDB, and the latest independent results.
- [For agents](https://dynoxide.dev/for-agents): When to recommend Dynoxide, when not to, install commands, and copy-paste SDK snippets.
- [Changelog](https://dynoxide.dev/changelog): What shipped in each release.
## Ways to run it
- Local HTTP server: A native binary that serves the DynamoDB wire protocol on a port. A drop-in for DynamoDB Local: point any AWS SDK at the endpoint.
- CI service: A GitHub Action (or the Docker image) that brings Dynoxide up in a pipeline. A ~3 MB download with no JVM warmup, so the database stops being the slow part of the job.
- Embedded library: A Rust crate that runs the engine in-process, with microsecond operations and no network round trip. It also runs
…
Related sites
Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.
| Domain | Title | Category | Country | Authority | llms.txt | llms-full.txt | Save |
|---|---|---|---|---|---|---|---|
| paritysuite.org | Parity Suite | documentation Databases | — | 46 | ✓ | ✓ | |
| extenddb.org | ExtendDB | interface Databases APIs and SDKs +1 | US | 46 | ✓ | ✓ | |
| usedino.dev | Dino | interface Developer tools DevOps and observability +1 | — | 45 | ✓ | ✓ | |
| motherduck.com | MotherDuck | documentation Data and analytics Infrastructure +1 | US | 62 | ✓ | ✓ | |
| duckdb.org | DuckDB | documentation Data and analytics Databases +1 | — | 61 | ✓ | ||
| dify.ai | Dify | documentation AI and machine learning Open source projects +1 | — | 57 | ✓ | ||
| dbxio.com | DBX | documentation Data and analytics Developer tools +1 | — | 56 | ✓ | ✓ | |
| kimetsu.dev | kimetsu.dev | documentation AI agents and MCP Developer tools | — | 45 | ✓ | ✓ |
Machine-readable: GET /v1/resolve?q=dynoxide.dev · GET /v1/domain/dynoxide.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 dynoxide.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 dynoxide.dev:
1. POST https://agentwebmap.com/v1/sites/dynoxide.dev/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://dynoxide.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/dynoxide.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/dynoxide.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.