OPEN DESIGN
Procurement & Security Leave-Behind · 2026
B2B Sales · Buyer-Committee Leave-Behind

Open Design
Approve Once, Deploy Everywhere

A forwardable one-pager-plus for security, procurement, and finance — what changes, what it costs, and what to sign off on.

Apache-2.0 · Self-hosted · BYOK · No data leaves your network
github.com/nexu-io/open-design · Prepared for buyer-committee review
Fig. 00 — Leave-Behind Overview
OPEN DESIGN
Contents
What's Inside

Contents

01 The Buyer's Pain Pain — Why the Current Setup Fails the Committee
02 Cost of Staying As-Is Cost — What the Status Quo Actually Bills
03 Proof Against the Incumbent Proof — Scored on Security, Cost, Ecosystem
04 How It Runs & What It Costs Architecture & Numbers
05 Rollout & the Ask Rollout — Pilot to Committee Sign-off
Open Design · Buyer-Committee Leave-Behind
Index
OPEN DESIGN
01 · Buyer Pain
The Buyer's Pain

Design tools your committee
keeps sending back to legal.

Cloud-only design AI means every prompt, file, and brand asset leaves your network — three separate blockers stall the deal before it reaches a signature.

Security
Data residency is a hard no

Vendor can't confirm where prompts and design files are processed or stored — InfoSec rejects the DPA before it reaches redlines.

Procurement
Per-seat pricing won't scale

$500/seat/month cloud licensing turns a 40-person design org into a line item finance flags every renewal cycle.

IT
No way to audit agent access

Closed-source agents give IT no visibility into what the model can read, write, or exfiltrate from a managed device.

Open Design · Buyer-Committee Leave-Behind
Sec. 01 — Buyer Pain
OPEN DESIGN
02 · Cost of As-Is
Cost of Staying As-Is · Annual
$248K/yr
What a 40-seat design org pays today in cloud design-AI licensing, security review overhead, and delayed procurement cycles.
6wk
Avg. security review delay per vendor
40seats
Locked to $500/seat/mo licensing
0
Audit logs on agent file access today
3×
Renewal escalations flagged by finance
Source: internal procurement records, illustrative
Fig. 01 — Cost of the Status Quo
OPEN DESIGN
03 · Proof
Proof Against the Incumbent

Scored on the axes
your committee actually checks

Security & control, local workflow, and agent ecosystem — the three questions InfoSec, procurement, and engineering ask before signing.

OPEN DESIGN · Committee Scorecard
Key Finding
On every axis a buyer committee checks — data control, local execution, agent auditability — the self-hosted, BYOK model outscores the closed cloud-only suite (demo scores).
Data: illustrative demo scores
Committee Scorecard — 03 axes
Open Design
Closed cloud suite
Industry average
100 80 60 40 Data Control License · BYOK · Self-host Local Workflow Local · Sandboxed Auditability 21 CLIs · BYOK 96.2 91.4 87.5 Fig. 02 — Committee Scorecard (Demo)
Data Control
License · BYOK · Self-host
96.2
+7.6 vs closed cloud suite
Cloud suite: 88.6 Avg: 84.1
Local Workflow
Files · Terminal · Sandbox
91.4
+15.2 vs closed cloud suite
Cloud suite: 76.2 Avg: 68.9
Agent Auditability
21 coding agents
87.5
+8.2 vs closed cloud suite
Cloud suite: 79.3 Avg: 72.4
OPEN DESIGN
04 · The Proposed Change
The Proposed Change

Data never leaves the network boundary

MANAGED DEVICE LOCAL DAEMON DELIVERABLES BYOK agents ×21, audited Sandboxed, logged execution Files stay on your own storage Fig. 03 — Data Boundary Map
Managed device

Your own Claude, GPT, or other model keys (BYOK) run under IT's existing device management — no vendor-side key custody.

Local daemon

Every agent action executes in a sandbox on infrastructure you control, with a full, exportable access log for security review.

Deliverables

Prototypes, decks, and dashboards are written to your storage as plain files — nothing round-trips through a vendor cloud.

Open Design · Buyer-Committee Leave-Behind
Sec. 04 — The Proposed Change
OPEN DESIGN
04 · Proof by the Numbers
Proof · Apache-2.0, Independently Verifiable

The numbers legal and finance will check

GitHub Stars
Open Source
60K+
Apache-2.0 — auditable source
Community
Contributors
300+
Independent code review
Ecosystem
Plugins
217+
No single-vendor lock-in
Design Systems
Brand context
129
GitHub · Figma · Local
Data Egress Events
Prompts & files, self-hosted
0
No vendor cloud in the loop
Annual Cost vs Status Quo
BYOK, 40-seat org
−80%
$248K/yr → ~$50K/yr
Source: github.com/nexu-io/open-design
Fig. 04 — Committee Proof Cards
OPEN DESIGN
Security Sign-off
First design tool we approved without
a single redline on the DPA.
Head of Security Review
Reference deployment, 40-seat design org
Open Design · Buyer-Committee Leave-Behind
Sign-off — Security Review
OPEN DESIGN
05 · Rollout
Rollout · Pilot to Committee Sign-off

A rollout your committee can pace

Week 1 · Pilot
One team, one machine

Install on a single design team's existing hardware with their own model keys — no procurement ticket required to start.

Week 2-3 · Review
Security & legal walk-through

Hand InfoSec the source repo, license, and access logs directly — no vendor NDA gate between them and the code.

Week 4 · Expand
Roll out to the design org

Same install, same BYOK keys, same audit trail — scale from 1 seat to 40 without a new licensing negotiation.

Ongoing · Renew
No annual re-negotiation

Apache-2.0 means there is no renewal clock — budget owns the model spend, not a per-seat license.

Open Design · Buyer-Committee Leave-Behind
Fig. 05 — Rollout Plan
OPEN DESIGN
Thank You
The Ask

Approve a 30-day pilot

No purchase order, no per-seat contract — one team, one machine, a decision by the next committee meeting.

Install Open Design (macOS / Windows) · Review the source on GitHub
github.com/nexu-io/open-design · discord.gg/mHAjSMV6gz · x.com/nexudotio
End — Fig. 06 — Commercial Ask
01 / 10
←/→ · Space