kernflux.github.io valid

OpenDsec

Open-source sandboxes on your own machines for RL rollouts and code-executing AI agents. Firecracker microVMs in ~0.1 s, fork with memory, and an E2B-compatible API.

For agents: Open-source self-hosted sandboxes using Firecracker microVMs for RL rollouts and code-executing AI agents, with an E2B-compatible API and Python SDK.

firecracker microvmcode sandboxe2b compatiblerl rolloutsself-hosted sandbox

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-25T04:55:37.663Z. Cached copy · Source on kernflux.github.io

# OpenDsec

> Open-source sandboxes on your own machines for RL rollouts and code-executing AI agents. Firecracker microVMs in ~0.1 s, fork with memory, and an E2B-compatible API.

OpenDsec is open source (AGPL-3.0) and implements the paper DeepSeek Elastic Compute (DSec), arXiv:2609.22978. It is an independent project, not affiliated with DeepSeek. Source code: https://github.com/Kernflux/opendsec. Every page below is also served as Markdown at the linked .md URL; the documentation exists in English and Chinese.

Highlights:

- microVMs in about 0.1 s: A Firecracker VM cold-starts in about 0.1 s, is created from a memory snapshot in about 55 ms, and resumes from a pause in about 50 ms.
- Fork and memory snapshots: fork(count=N) clones a running VM with its memory, pausing the source for about 10 ms. Copies on one node share pages; other nodes pull from the source node.
- Pause a whole task: When training is preempted, pause every sandbox of a task and release its memory. The next call to a paused sandbox resumes it.
- E2B compatible: Code written for the E2B SDK runs after changing three environment variables, including commands, files, PTY, ports, snapshots and the code interpreter.
- Layered images: Import from any OCI registry, compose layers without copying, and save an environment with pack_diff. The store lives on NFS, CephFS or JuiceFS.
- Default-deny network: Allow traffic by domain, CIDR and port per sandbox, changeable while it runs. Enforced with nftables and a DNS proxy.
- Isolation: A jailer with a uid per VM, core scheduling against SMT side channels, seccomp, read-only agents and per-session users.
- Projects and quotas: Nested projects, hierarchical quotas and bounded delegation. Raft-replicated IAM, mTLS between components, short-lived revocable tokens and audit logs.
- Operations: Staged fleet rollouts with automatic rollback, an offline bundle, Prometheus metrics and alerts. Upgrading any component leaves running sandboxes alone.

## Docs

- [Docs](https://kernflux.github.io/en/docs/index.md): OpenDsec documentation: installation and deployment, the Python SDK and CLI, images and snapshots, network policy, permissions, operations and monitoring, organized by task.
- [Get started](https://kernflux.github.io/en/docs/quickstart.md): Install every OpenDsec component on one Linux machine, then create sandboxes with the Python SDK, the E2B SDK or the command line.
- [Concepts](https://kernflux.github.io/en/docs/concepts.md): This page introduces every concept you meet when using OpenDsec: sandboxes and their backends, lifecycle and timeouts, sessions, tasks, images and snapshots,…
- [FAQ](https://kernflux.github.io/en/docs/faq.md): OpenDsec FAQ: what it is, a self-hosted E2B alternative, microVM vs container isolation, how many sandboxes a cluster runs, RL training, Kubernetes, licensing, KVM, GPUs and production readiness.
- [OpenDsec vs E2B, Daytona and Modal](https://kernflux.github.io/en/docs/compare.md): How OpenDsec compares w
…

Related sites

Explore similar publishers →

Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.

Machine-readable: GET /v1/resolve?q=kernflux.github.io · GET /v1/domain/kernflux.github.io · 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.

Claim my listing on Agent Web Map for kernflux.github.io:
1. POST https://agentwebmap.com/v1/sites/kernflux.github.io/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://kernflux.github.io/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/kernflux.github.io/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/kernflux.github.io).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.