Independent reviews. IonBin has no partnerships with the tools on this page and was not paid for these listings. Our evaluations are our own, based on public documentation and our research. Product names are trademarks of their owners and are used for identification only. How disclosure works.

Design systems / AI design workspace

Fudge

Bring references, website feedback and design work into a conversational workspace.

Documentation reviewed

Source review

What this status means

Understand the resource

What it is.

Fudge now presents a conversational design workspace with a message field, file attachment control and links to a workspace and integrations. The earlier design.withfudge.com address redirects here; DESIGN.md extraction and token exports are not established by the current public interface.

When it is useful

A team needs to turn references and design feedback into a more concrete direction before implementation.

A proposed application

Put it to work.

This example illustrates a possible use. The proposed workflow and expected result are separate from the bounded checks recorded below.

Try this

Start with an approved public reference and three spacing or hierarchy questions; confirm the workspace's data handling and output options before submitting real project material.

Result to aim for

A clearer design brief; generated output and export availability still need a separate account-based check.

Before you start

What you need.

  • A browser; Google and email sign-in options are offered for an account.
  • Permission to share any reference URL, file or design content submitted to the workspace.

The practical boundaries

What to watch for.

  • The visible workspace does not establish supported design-file exports or generated-code quality.
  • The public page loads several analytics and marketing services; review data handling before entering confidential material.

Review record

What we could establish.

  • The current workspace and account menu were inspected in a fresh browser. No message, file, account or integration workflow was submitted.
Source coverage and runtime coverage are separate

The source-review notes describe documentation and identity. The account-free evaluation below records exactly which public interaction or local fixture was checked, what happened, and what remains untested.

Check current access, terms, licensing and data handling before using a resource with your own material.

Runtime and security evaluation

What the evaluation covers.

Limited evaluationAccount-free ·

The current workspace and account menu render; the earlier address redirects successfully. Message processing, attachments and integrations remain outside this account-free test.

Methods: Public HTTP response · Public browser sample · Source review. A completed check covers the stated sample; it is not a safety certification.

Target
https://fudge.design/
Version or capture
Unversioned public page observed 2026-10-19
Integrity scope
SHA-256 63c5fa67aa2c0c4a727718eb5fd279e45548b0523cd84322ad2bd37ac07c5c27 of one initial HTML response (13718 bytes). This does not fingerprint the entire application or its dependencies.

Test conditions

  • Windows; Chrome 155.0.8059.82 headless via Playwright, fresh isolated contexts with a 1365 × 900 viewport.
  • Reduced motion requested. GET/HEAD requests allowed; other methods and WebSocket connections blocked.
  • No owner browser profile, account, credentials, purchase, upload, private fixture or service write.

Individual checks and observations

  1. Current address and redirect

    pass

    Public browser sample: Open fudge.design and design.withfudge.com in separate fresh browser contexts.

    Observed: Both ended at fudge.design with HTTP 200 and the current workspace UI.

  2. Account boundary

    pass

    Public browser sample: Open Account menu without typing an email or choosing a provider.

    Observed: An account dialog offered Google sign-in and an email-code flow.

  3. Message and attachment processing

    not-run

    Public browser sample: Do not submit messages or files; inspect the public controls only.

    Observed: A message textarea and attachment control were visible, but no processing or output was tested.

Security findings and boundaries

Public workspace navigation, response headers, request destinations and the unsubmitted account menu.

Observed · caution

Public page contacts multiple third parties

The initial page requested analytics/marketing origins including Clarity, PostHog, Google Tag Manager and Reddit-related hosts. Non-GET requests were blocked; no prompt or file was submitted. This reveals a broader page data-flow surface, not a finding about uploaded-content retention.

Practical advice · caution

Inspect data sharing before using real work

Check which reference files, URLs and agent integrations are shared with the service and its subprocessors before bringing private projects into the workspace.

Practical caveats

  • Treat the current product as a workspace; confirm a specific export format before building a workflow around it.
  • Account-menu access is not evidence that a generation or integration succeeds.

What remains untested

  • No account, prompt response, attachment, agent connection, export or workspace-permission test.
  • The write-blocking browser guard can alter analytics and other application behavior.

Security limits

  • Passive public-page observations and the stated bounded sample only; no exploitation, authenticated authorization, backend, retention or comprehensive dependency audit.
  • Request blocking changes application behavior; no secure/safe certification is implied.

Evaluation sources

  1. Current public workspace
  2. Earlier address; redirect checked

Download this evaluation record (JSON)

Follow the evidence

Sources and further reading.

  1. Current public workspace
  2. Earlier address; redirect checked

Keep exploring

More in design systems.

View category

Documentation reviewed

Refero Styles

Turn a visual reference into a starting system an agent can read.

Documentation reviewed

DesignMD

Inspect a website’s visual system before drafting new screens.

Documentation reviewed

designmd.supply

Create a design brief from a public website’s available visual data.