THE PROTOTYPE GUIDE
Know what’s real.
Explore what’s next.
A practical guide to this Foundry website: what the interactive samples do, what remains a product vision, and how your information is handled.
The prototype and the vision.
Foundry is a fictional AI startup presented through a working website prototype. Navigation, browser interactions, and local sample demonstrations are real. The AI platform described by the product pages is a proposed future system.
Start with the experience.
- 01
Explore a question in context.
Open the workspace sample and use its provided controls to explore an illustrative business question. Responses and source material are local samples.
- 02
Inspect the process.
Try the workflow builder to explore a sequence of steps. The interface demonstrates a process; it does not execute work outside your browser.
- 03
Look at a structured result.
Visit the developer playground, copy the proposed interface, and select “Run example.” The prewritten JSON response is revealed locally.
Local by design.
The interactive demos use illustrative sample data and browser state. They do not upload files, retrieve private knowledge, send prompts to a model, or trigger external automations. A loading animation indicates a simulated interaction, not live inference.
“Run example” is a simulation.
The developer example shows the same prewritten response each time. Its model_called field is false, and its mode is local_simulation. Copying copies code text to your clipboard; it does not execute the code.
Do not paste sensitive business information into this prototype. No real data is needed to explore the samples.
No live AI endpoints.
The foundry.run() interface on the developer page is a fictional API design. There is no installable Foundry SDK, API key service, live AI inference endpoint, or production workflow API supplied by this prototype.
Claude is a planned model integration, not a connection currently running on the site. The name identifies an intended model choice; it does not imply a partnership or endorsement by Anthropic.
Authentication, structured outputs, tool permissions, webhooks, and knowledge connectors are described as design goals. Do not build a production dependency on the illustrative code.
Review the proposed architectureA submission is not always a delivery.
The contact and demo-request forms are controlled by the browser and attempt a same-origin form submission. Their result message tells you whether your details were saved locally or accepted by a configured backend. This form handler is not an AI endpoint.
Saved in this tab.
Without a configured storage backend, submitted details are saved to sessionStorage for the current browser tab. They can remain across reloads in that tab, but are not delivered to a Foundry team or inbox. Closing the tab normally ends the session; browser restore behavior can vary.
Stored by a configured deployment.
A deployment can bind a Cloudflare KV namespace named SUBMISSIONS. When configured and accepted, contact fields are stored with a 30-day expiration. Storage does not itself mean an email was sent, a meeting was booked, or someone will respond.
If a form reports a problem, do not assume a remote submission succeeded. Never enter passwords, payment details, confidential documents, or other sensitive content.
Read the form privacy detailsSimple interactions. Clear boundaries.
This prototype does not include an analytics or tracking SDK. Its licensed fonts are served from the same website; there is no runtime request to an external font provider. Hosting providers may process normal request metadata.
Interactive sample content stays local. Form information follows the local or configured-backend behavior described above. The privacy notice explains these distinctions without claiming production-grade privacy or regulatory certifications.
Useful to explore. Not ready to rely on.
- No real inference, external workflow execution, or document ingestion.
- No customer accounts, organization management, billing, or active API credentials.
- No asserted customers, business traction, partnerships, or security certifications.
- No guaranteed response to a contact or demo request.
- No legal, financial, compliance, or other professional advice.
Any future production implementation would need separate evaluation, security controls, operating policies, and appropriate agreements. The prototype terms describe the boundaries of this demonstration.