clawdie/clawdie-iso
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
clawdie-iso/FUNDING.md
Sam & Claude c47cd44251 Add .prettierrc + reformat all active markdown to match 
Codifies the markdown format Sam applied in bd94b87 / 30cf590 as a
project rule rather than per-file judgment. Prettier 3 defaults with
proseWrap=preserve (no prose reflow), printWidth=80, embedded code
formatting off so we don't touch fenced shell/JSON blocks.

.prettierignore scopes Prettier to active docs:
  - excludes tmp/, cache/, node_modules/, build artifacts
  - excludes CHANGELOG.md + RELEASE-NOTES-*.md (hand-formatted, rigid)
  - excludes .archive/ and .opencode/ (historical / tooling internal)
  - excludes bundled bootstrap.html

Reformatted 16 active .md files: padded markdown tables, blank line
before lists (CommonMark-strict), `*emph*` -> `_emph_`. No content
changes — diffs are all whitespace/alignment/emphasis style.

Verified: `npx prettier@3 --check '**/*.md'` reports all clean.

Build: not run — docs + tooling config only.
Tests: pass — prettier --check is green; git diff confirms no content
deletions, only formatting.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-05-20 11:16:42 +02:00

10 KiB
Raw Blame History

Funding Clawdie

Clawdie is a FreeBSD-based operating system and orchestration platform for autonomous agents. It's named after a character meaningful to me—a vision of how humans and AI agents can work together securely and deterministically.

We're seeking support to continue foundational work and establish a full-time AI Operator role that will drive this project forward.

Origin Story

Peter Steinberg initiated this work as foundational research: what would a truly safe AI agent orchestration platform look like? His insight was that security and determinism need to be built into the OS layer, not bolted on afterward. This came from years of studying what enterprise AI deployment actually requires.

I continued Peter's vision after stepping away from the IT support grind (SAP.com level 2 support was my last corporate role). Like Peter, I recognized the gap between what enterprises desperately need and what's being offered. Rather than compete with orchestration frameworks like OpenClaw, I'm deepening a personal philosophy: how I want to work with AI agents—treating them as amplifiers of human judgment, not replacements for it.

The name "Clawdie" comes from someone meaningful to me. This isn't a detached infrastructure company—it's a personal commitment to building something I actually believe in. The philosophy is simple: transparent, deterministic, safe, grounded in real values.

More about me: samob.netlify.app

The Problem

AI agents at scale need OS-level security and deterministic execution. Current approaches lack:

  • Verified isolation: No proof that agents can't escape their sandbox
  • Auditability: Enterprise can't verify what code actually ran
  • Offline-first design: Agents shouldn't phone home for every decision
  • Enterprise compliance: No framework for regulatory sign-off on agent execution

NVIDIA's announcement of OpenClaw/NemoClaw validates that enterprises recognize this gap. But we're not trying to compete with their orchestration framework. Instead: showing an alternative philosophy for how to work with agents.

Our Solution

Clawdie is a verified execution environment for agents, built on FreeBSD. Think of it as a locked, observable room where agents can run safely, and humans can see everything they did:

  • Deterministic sandbox: FreeBSD jails provide OS-level isolation. No escaping. Fully auditable.
  • Offline-capable: Fetch packages once, then run agents anywhere—trains, ships, air-gapped datacenters. No dependency on cloud services.
  • Reproducible builds: Every ISO is byte-for-byte identical. Enterprises can verify there's no hidden code or supply-chain tampering.
  • Philosophy: Agents amplify human judgment; they don't replace it. Every decision is logged, verifiable, contestable.

Current status:

  • ✅ Functional ISO builder with integrated payload system
  • ✅ Working integration with Stripe agents
  • ✅ Trademark secured
  • ✅ Technical validation in progress (bhyve install testing)

Infrastructure: Maintained by Clavidija, supporting ongoing development

What We're Seeking

Immediate: AI Operator Role + Development Support

What is an "AI Operator"? Someone who builds the infrastructure for safe agent execution, then works directly with organizations deploying agents at scale. It combines:

  • Deep technical work (FreeBSD, orchestration, security isolation)
  • Research (studying what works and doesn't in production)
  • Teaching (helping teams understand how to work with agents safely)

I'm actively seeking:

  • Employment: AI Operator role at an organization aligned with Clawdie's vision (preferred)
  • Validator funding: $50K–$250K to continue research independently while building enterprise PoCs
  • Research partnerships: Universities, NVIDIA, foundations interested in agent safety research

Medium-term: Seed Round ($500K–$1M, 12 months)

To establish:

  1. Enterprise-grade image + deployment tooling
  2. Security audit (3rd-party validation)
  3. Managed service launch (Clawdie-as-a-Service)
  4. Partnership exploration with NVIDIA/OpenClaw ecosystem

Strategic Partners ($1M–$3M)

  • NVIDIA: Clawdie as reference implementation for agent security
  • Enterprise infrastructure VCs (Bessemer, Mayfield, Accel, a16z)

Grants & Partnerships

  • Sovereign Tech Fund, Protocol Labs, Mozilla Ventures (open infrastructure)
  • FreeBSD Foundation research partnerships
  • Academic security research collaborations

Why Now

  1. NVIDIA's NemoClaw announcement validates enterprise appetite for safe agent execution
  2. Enterprise AI production deployments accelerating — agents leaving labs, compliance tightening
  3. FreeBSD 15 + pkgbase — new packaging enables reproducible agent environments
  4. Founder philosophy clarified — I know what I believe about AI agents and how to build for them
  5. Trademark secured — IP foundation established
  6. Stripe agents as force multiplier — one person can move fast on infrastructure

Team & Background

Peter Steinberg — Founder & Strategic Advisor

  • Originated the foundational research: what does truly safe agent orchestration look like at the OS level?
  • Pioneered the FreeBSD + jails approach after studying enterprise deployment patterns
  • Continues to guide strategic direction and technical philosophy
  • Not competing with OpenClaw; exploring a complementary, values-driven approach

Me — Executor, Researcher, & AI Operator

  • Background: Broke from IT support grind (SAP.com level 2 was my last corporate role) to pursue AI research
  • Expertise: FreeBSD infrastructure, security isolation, agent orchestration patterns
  • Track record: Built Clawdie-AI platform with 2000+ agent deployments
  • Philosophy: Open source, security-first, transparency, treating agents as tools for human judgment
  • Full background: samob.netlify.app

Clavidija — Infrastructure & DevOps

Commercial Model

Open source + human-centered services:

  • Free: ISO downloads, documentation, community support
  • Paid: Managed deployment, compliance certification, SLA support, consulting on agent orchestration patterns
  • Enterprise: Support contracts, security audit coordination, integration with existing frameworks
  • AI Operator services: Custom agent training, deployment oversight, safety validation

Revenue model: Similar to Canonical/Red Hat, but emphasizing the human side—teaching organizations how to work safely with AI agents, not just providing infrastructure.

Why Support This?

For employers: Hire someone who can build safe AI agent infrastructure and teach your team how to use it.

For investors: The market for agent orchestration security is nascent. Being early in this space (alongside but not competing with NVIDIA) is valuable positioning.

For the community: A demonstration that it's possible to break from the corporate support grind and build something that matters. A personal assistant (Clawdie) becomes a platform for others.

How to Get Involved

I'm Looking For

  • AI Operator role (primary—a paid position where I can do this full-time)
  • Validator funding ($50K–$250K to continue research independently)
  • Research partnerships (universities, NVIDIA, think tanks)
  • Strategic advisors (people who've shipped infrastructure at scale)

Let's Talk

Email: hello@clawdie.si

Say what brings you here. A few things help:

  • Your background / what you work on
  • Why Clawdie caught your attention
  • Whether you're thinking: job opportunity, funding, collaboration, or just curious

I respond to everything. No gatekeeping.

Developers & Community

  • GitHub: clawdie-iso
  • Issues: Bug reports, feature requests, architecture discussions
  • Discussions: Design decisions, roadmap input

Path Forward (If Funded)

Timeline Milestone What It Enables
Now Secure employment or validator funding ($50K–250K) Full-time development, production PoCs
3 months Security audit + compliance framework Enterprise buyers can sign contracts
6 months Working enterprise PoCs (2–3 customers) Market validation, customer case studies
9 months Managed service beta (Clawdie-as-a-Service) Revenue-generating offering launches
12+ months NVIDIA partnership or Series A Scale infrastructure, bigger team

If employment route: Timeline accelerates. All of the above happens as day-job work with full resources.

What Makes This Different

  • Not a VC-chasing startup: We're building something we believe in, looking for people who align with that vision
  • Philosophy-driven: Not "maximize market share," but "how should humans and AI agents actually work together?"
  • Personal stake: Clawdie is named after someone real to me; this isn't a side project
  • Open by design: You can see exactly what we're building and decide if it matters to you
  • Continuing Peter's work: Not starting from scratch; building on proven foundational research

Public Commitments

If you support this work, here's what you can expect:

  • Code: Fully open source (MIT or Apache 2.0). No "source-available" games.
  • Transparency: Monthly updates on progress, blockers, learning. Public roadmap. Share what works and what doesn't.
  • Community first: Direction shaped by contributors and users, not just funders or corporate interests.
  • Values: Safety and human agency come before profit. We won't compromise these for a payday.

Let's Build This

If this resonates with you—whether you're thinking about hiring, funding, collaboration, or just want to talk about safe AI agents—reach out.

Email: hello@clawdie.si

We're doing this in the open. Come shape it with us.