What brings you here?
Pick the closest starting point. There is no wrong answer, and you can change it at any time.
Recommended paths
Popular paths through OFO
Build a one-page site with FreeWebStore, create a logo and brand kit in FreeDesignStore, then plan your launch and social content in FreeMarketingStore.
Learn gates, ALUs, pipelines, caches, GPUs, and CPU architecture in FreeChipStore. For volunteer experience, improve a simulation, test its technical accuracy, or contribute documentation through GitHub. OFO does not currently place volunteers with semiconductor companies.
Choose Robotics, Quantum, Chips, Space, Biology, or Crypto Systems. Share direct simulation links, review assumptions first, and build a lesson around changing parameters and explaining results.
Prototype or publish a PWA through FreeAppStore. Use ProAppStore only when the project needs server AI, databases, uploads, scheduled jobs, or stronger operational support.
Choose one technical store, complete a focused simulation or tool improvement, document what you learned, and publish the work as an open-source contribution or portfolio project.
Writers, musicians, designers, and content creators can combine Writing, Books, Music, Design, Marketing, and Web stores into a complete creation-to-audience workflow.
Free or Pro?
| Question | Free is usually right when... | Pro is usually right when... |
|---|---|---|
| Execution | The core workflow can run in the browser. | It needs durable server compute or background work. |
| Data | Local or small per-user storage is enough. | You need a database, larger storage, uploads, or shared state. |
| AI | Your device, browser model, or own API key is acceptable. | You need managed inference, quotas, automation, or server orchestration. |
| Collaboration | Single-user or lightweight rooms are enough. | You need teams, persistent collaboration, or higher real-time limits. |
| Identity | No account or simple sign-in is acceptable. | You need ownership, roles, billing, licenses, or organization controls. |
| Operations | Best-effort public hosting is acceptable. | You need support, custom domains, scheduled jobs, or managed operations. |
| Source | MIT-licensed public source fits the project. | Proprietary source or commercial service terms are required. |
Pro availability and pricing are product-specific until paid services are fully launched. The planned shared subscription model is not a guarantee that every preview currently accepts payment or provides every documented capability.
How to read status labels
- Production
- A deployed, actively operated core workflow with meaningful tests and release infrastructure. It does not imply an SLA, formal certification, or zero defects.
- Production with caveats
- The product is usable, but a known architecture change, support limitation, or incomplete subsystem materially affects evaluation.
- Post-beta
- A functioning public product beyond initial beta, but with quality, SDK, documentation, or operational work below the strongest production stores.
- Early beta
- Deployed and testable, but APIs, reliability, data handling, catalog quality, and UX can change significantly.
- Preview
- A public demonstration of direction. Some screens or backend pieces work, but the end-to-end service may be incomplete.
- Scaffold
- Repository, package, template, or storefront foundations exist. Evaluate it as development work, not a dependable user service.
- Planned
- A documented idea or roadmap item without a complete public implementation. Timing and scope can change.
- Retired
- No longer actively operated. Source and migration guidance should remain available where practical and legally permitted.
Accounts, browsers, devices, and data
No-account experiences
Most static simulations and focused tools open directly. They may store preferences or work in your browser. Export important work because local browser storage is not a backup.
Account-based experiences
Publishing, ownership, synchronization, roles, collaboration, marketplaces, billing, and some storage services require identity. The sign-in provider and account controls vary by store.
Browser capabilities
Modern baseline features work across current Chromium, Firefox, and Safari. WebGPU, browser-built-in AI, advanced file access, PWA installation, audio processing, and some codecs are less uniform.
Performance
Large local AI models, 3D simulations, audio workstations, and data tools can consume substantial memory, storage, battery, and download bandwidth. Mobile support does not imply every workload is comfortable on a phone.
Data sensitivity
Use public tools for non-sensitive work unless a product clearly documents stronger controls and suitable terms. Read the privacy overview before using accounts, uploads, external AI, or regulated data.
For schools, teams, and organizations
Classroom use
Direct links and no-account simulations reduce setup. Educators should review accuracy, accessibility, browser support, and external requests.
Team use
Do not assume public tools include centralized administration, retention policy, audit logs, or contractual support. Evaluate the exact Pro product.
Procurement
Public availability is not an enterprise agreement. Confirm billing, cancellation, data processing, security, support, and service levels in writing.
Self-hosting
MIT-licensed repositories can usually be self-hosted, but deployment complexity and third-party licenses vary. Hosted service and source are separate propositions.
Common limitations
- Repository, registered-item, deployed-item, and visible-catalog counts are not interchangeable.
- A useful tool is not automatically validated for high-stakes decisions.
- Open source does not make every bundled asset or model unrestricted.
- Free hosting does not imply guaranteed indefinite availability.
- AI output can be plausible and wrong; local execution improves privacy, not truthfulness.
- A polished preview can exist before all underlying operations are complete.
Glossary
- Store
- A domain-focused public catalog and product identity, such as FreeAppStore or FreeRobotStore.
- Platform
- Shared infrastructure for a store: SDK, CLI, backend, host, admin, publishing, compliance, and tests.
- Item
- One app, game, site, agent, tool, or simulation listed in a store.
- PWA
- A web application supporting app-like behavior through browser standards, sometimes including installation and offline assets.
- Worker
- Server-side code running on Cloudflare's edge platform.
- D1
- Cloudflare's managed SQL database used by several platform products.
- R2
- Cloudflare object storage used for apps, assets, uploads, and generated content.
- Durable Object
- A stateful Cloudflare runtime primitive used for rooms, agents, conversations, and coordination.
- SDK
- A library exposing store services such as auth, storage, rooms, AI, roles, and notifications.
- CLI
- A command-line tool used to scaffold, validate, publish, diagnose, or manage products.
- Compliance check
- An automated rule covering brand, security, bundle size, accessibility, viewport behavior, or prohibited tracking.
- Registry
- Structured catalog data connecting item identity, routes, metadata, source, and storefront generation.