Find your ingredients.
Explore recipes by model or topology. Read the notes, review the configuration, and choose a version that fits what you want to try.
Explore recipes Back to the recipe shelf01 02 03 FROM THE SHELF TO YOUR WORKSPACE SMALL CHANGES, CLEAR ROOTS CONTRIBUTE WITH CONTEXT ABOUT THIS PREVIEW
A SHARED NOTEBOOK, ONE RECIPE AT A TIMEA place to start.
A place to start.
A way to build on it.
TwinSpark Community brings model configurations and their history together, so the next experiment can start a little further along.
Make room to experiment.
Download a JSON recipe and review it in your own workspace. Every setup is different; validate model access, hardware, and runtime settings locally.
A recipe is a starting point.Leave a useful trail.
Share your configuration or fork an existing recipe. Add honest notes, credit the original, and let a clear version history tell the story.
Share a recipeUse a recipe
- Download a specific version.
Recipe pages provide an exact JSON file and its SHA-256 fingerprint. The version link stays attached to that configuration.
- Review the configuration.
Check the model names, topology, context length, memory assumptions, and any extra launch settings. Templates are explicitly unbenchmarked.
- Import into TwinSpark Manager.
Use the Manager’s recipe import workflow, then validate it against your local setup before launching.
Versions, forks, and votes
A version records a recipe document and its change notes. View the history to see how the configuration evolved and compare field changes between versions.
A fork starts a separate recipe from an existing one. Its link to the original stays visible, giving credit and keeping the idea’s roots clear.
A vote signals that a contributor finds a recipe useful. It is not a benchmark, a verification badge, or a promise of performance.
Share something useful
Sign in with GitHub, upload or paste a TwinSpark recipe, and add a name, summary, license, and field notes. Explain what you tried and call out untested assumptions.
Submissions are checked and reviewed before publication. Leave out tokens, API keys, personal information, and configuration you do not have permission to share.
Community recipes share configurations. Model weights and access permissions remain with their original providers.
Explore first. Contribute securely.
When this site is served over HTTP, it operates as a read-only preview. You can browse recipes, inspect versions, compare changes, and download JSON.
GitHub sign-in, submissions, forks, and voting require HTTPS and configured GitHub authentication. These controls explain their availability throughout the preview.
The starter recipes are templates. They help demonstrate the format and have not been benchmarked on your hardware.
Take a starting point.
Leave a better one.