fencesandbox.com is built with Next.js, hosted on Cloudflare. It measures traffic with Cloudflare Web Analytics.
| Technology | Version | First seen |
|---|---|---|
| JavaScript Frameworks & Libraries2 | ||
| 16.2.4 | 9 Nov 2026 | |
| – | 9 Nov 2026 | |
| Frontend Build Tools & CSS4 | ||
| – | 9 Nov 2026 | |
| Web Servers, Languages & Backend Frameworks1 | ||
| CDN & Hosting1 | ||
| – | 9 Nov 2026 | |
| Analytics & Tag Management1 | ||
| – | 9 Nov 2026 | |
| Fonts & Icon Fonts2 | ||
| – | 9 Nov 2026 | |
Registration from the registry's RDAP record, the certificate the site serves, and its rank in public traffic lists.
The crew hasn’t read this site’s colors yet. We read a palette when we capture a site’s screenshot, busiest sites first. Meanwhile, browse palettes from other sites.
Counted from every stack change we've recorded: of the sites we watched running one of this site's tools, how many went on to add another. A pattern across sites, not a forecast for this one.
fwd1.porkbun.comfwd2.porkbun.comcarioca.ns.cloudflare.comvick.ns.cloudflare.comv=spf1 include:_spf.porkbun.com ~all# As a condition of accessing this website, you agree to abide by the following # content signals: # (a) If a Content-Signal = yes, you may collect content for the corresponding # use. # (b) If a Content-Signal = no, you may not collect content for the # corresponding use. # (c) If the website operator does not include a Content-Signal for a # corresponding use, the website operator neither grants nor restricts # permission via Content-Signal with respect to the corresponding use. # The content signals and their meanings are: # search: building a search index and providing search results (e.g., returning # hyperlinks and short excerpts from your website's contents). Search does not # include providing AI-generated search summaries. # ai-input: inputting content into one or more AI models (e.g., retrieval # augmented generation, grounding, or other real-time taking of content for # generative AI search answers). # ai-train: training or fine-tuning AI models. # use: how AI systems may consume the content (immediate, reference, or full). # ANY RESTRICTIONS EXPRESSED VIA CONTENT SIGNALS ARE EXPRESS RESERVATIONS OF # RIGHTS UNDER ARTICLE 4 OF THE EUROPEAN UNION DIRECTIVE 2019/790 ON COPYRIGHT # AND RELATED RIGHTS IN THE DIGITAL SINGLE MARKET. # BEGIN Cloudflare Managed content User-agent: * Content-Signal: search=yes,ai-train=no,use=reference Allow: / # Training crawlers User-agent: Amazonbot Disallow: / User-agent: Applebot-Extended Disallow: / User-agent: Bytespider Disallow: / User-agent: CCBot Disallow: / User-agent: ClaudeBot Disallow: / User-agent: Diffbot Disallow: / User-agent: Google-Extended Disallow: / User-agent: GPTBot Disallow: / User-agent: omgili Disallow: / User-agent: anthropic-ai Disallow: / User-agent: Claude-Web Disallow: / User-agent: cohere-ai Disallow: / User-agent: MistralAI-Training Disallow: / User-agent: meta-externalagent Disallow: / User-agent: GoogleOther Disallow: / User-agent: Baiduspider Disallow: / User-agent: PetalBot Disallow: / User-agent: AwarioSmartBot User-agent: AwarioRssBot Disallow: / User-agent: Google-CloudVertexBot Disallow: / User-agent: QualifiedBot Disallow: / User-agent: Cotoyogi Disallow: / User-agent: ICC-Crawler Disallow: / User-agent: atlassian-bot Disallow: / User-agent: FishBot Disallow: / User-agent: BorderxBot Disallow: / User-agent: NavuBot Disallow: / User-agent: SemrushBot-SWA Disallow: / User-agent: WARDBot Disallow: / User-agent: magpie-crawler Disallow: / User-agent: KimiBot Disallow: / User-agent: CitibotSiteCrawler Disallow: / # END Cloudflare Managed Content
# Fence - [Introduction](/docs): Lightweight, container-free, configurable sandbox for running commands and terminal agents with network and filesystem restrictions. - [Why Fence?](/docs/why-fence): What problem Fence solves, where it fits, and what it doesn't try to be. - [Quickstart](/docs/quickstart): Install Fence and run your first sandboxed command. - [Concepts](/docs/concepts): The mental model behind Fence. - **Guides** - [Using Fence with AI agents](/docs/guides/agents): Apply a consistent permission layer across Claude Code, Codex, Cursor, OpenCode, and more. - [Agent hooks](/docs/guides/hooks): Use an agent's hook or plugin system to check and sandbox tool calls. - [Config templates](/docs/guides/templates): Built-in templates for common setups. - [Recipes](/docs/guides/recipes): Copy-paste starters for common workflows. - [Importing from Claude](/docs/guides/importing): Convert your existing Claude Code permissions into a Fence config. - [Troubleshooting](/docs/guides/troubleshooting): Common failure modes and how to fix them. - **Reference** - [Configuration](/docs/reference/configuration): The full reference for your fence.json. - [Go library](/docs/reference/library): Embed Fence in your Go program to sandbox commands programmatically. - [Security model](/docs/reference/security-model): Fence's threat model, what it enforces, and the limitations you should keep in mind. - [Linux security features](/docs/reference/linux-security-features): Landlock, seccomp, eBPF monitoring, and how Fence falls back gracefully when features are missing. - [Architecture](/docs/reference/architecture): How Fence resolves config, starts proxies, enforces policy, and wraps your command on each platform. - **Contributing** - [Get involved](/docs/contributing): Fence is actively developed and open to contributions — here's how to get started. - [Project structure](/docs/contributing/project-structure): Where the code lives in the Fence repository. - [Testing](/docs/contributing/testing): How Fence is tested — unit, integration, and end-to-end smoke tests on both platforms. - [Linux bwrap mount sequence](/docs/contributing/linux-bwrap-mount-sequence): How Fence assembles the layered bubblewrap mount list and why ordering matters.
| – |
| 9 Nov 2026 |
| – | 9 Nov 2026 |
| – | 9 Nov 2026 |
| – |
| 9 Nov 2026 |
| – |
| 9 Nov 2026 |