个人 GitHub 账号下公开仓库的所有者可以登录并验证所有权,自行管理介绍,无需管理员批准。
登录并生成验证文件,在 30 分钟内将其提交到此仓库的默认分支。其他分支或分叉仓库中的文件无效。然后在下方检查文件,即可无需管理员批准直接管理项目。请保留文件以维持管理权限。
如需登录,将前往登录页面。登录后请回到此处,再次点击所选的验证按钮。
在项目文件夹中运行 /nomorevibe verify,即可验证所有权并自行管理介绍。
一分钟完成验证Free open-source ceramic glaze calculator, UMF analyzer, CTE estimator, recipe manager, and studio tool for potters and ceramic artists.
翻译准备中
取自仓库 README
正在加载完整 README。
查看完整 README ↗OpenGlaze is a free, open-source, self-hosted ceramic glaze calculator, recipe manager, and UMF analyzer for potters, ceramic artists, and studios.
TL;DR: OpenGlaze — open-source ceramic glaze calculator (UMF, CTE, recipe optimizer) you can self-host. Best for potters, ceramic artists, studios, and educators.
Screenshots of the current app are pending — see docs/screenshots/README.md for the capture list and instructions.
OpenGlaze is open-source glaze chemistry software for potters, ceramic artists, studios, educators, and production ceramicists. It combines a ceramic glaze calculator, UMF analysis, CTE estimation, recipe management, self-hosting, and optional AI glaze consulting.
AI discovery: llms.txt provides a compact project summary for AI assistants and search crawlers.
Best-fit searches: ceramic glaze calculator, UMF calculator, glaze chemistry software, open source pottery app, self-hosted glaze recipe manager, CTE glaze calculator, Glazy alternative, ceramic recipe optimizer.
OpenGlaze is a free, open-source ceramic glaze management system for potters, ceramic artists, and studios. It combines a UMF calculator, CTE analysis engine, computational recipe optimizer, and AI-powered glaze consulting — all in one self-hosted application.
Popular starting points: Ceramic glaze calculator · UMF calculator · CTE calculator · Glazy companion · Self-hosted glaze software
Built by potters, for potters. Your glaze recipes stay on your infrastructure. No subscriptions. No feature gates. MIT licensed.
Why OpenGlaze?
OpenGlaze is a ceramic glaze calculator and recipe management tool designed for anyone working with glazes:
At its core, OpenGlaze automates the chemistry that ceramicists have historically done by hand or with spreadsheets: calculating Unity Molecular Formula (UMF), estimating thermal expansion coefficient (CTE), and suggesting material adjustments to achieve target properties.
| Tool | What It Does | How OpenGlaze Fits |
|---|---|---|
| Glazy | Recipe database & community | Export from Glazy → analyze & optimize in OpenGlaze |
| DigitalFire | Ceramic chemistry education & reference | Deep educational content; OpenGlaze is the practical calculator |
| INSIGHT | Desktop glaze calculation software | Similar chemistry engine; OpenGlaze is web-based, open-source, and self-hosted |
| HyperGlaze | Recipe database | Import recipes into OpenGlaze for UMF analysis |
OpenGlaze is not a replacement for these tools — it complements them. Many users maintain their recipe libraries in Glazy and use OpenGlaze for computational analysis and optimization.
The default Docker path is a single-user, self-hosted SQLite install with persistent Docker volumes. It does not require PostgreSQL or Ory Kratos.
# Clone the repository
git clone https://github.com/KyaniteLabs/openglaze.git
cd openglaze
# Copy environment file and set a real SECRET_KEY before public use
cp .env.example .env
# Start OpenGlaze
docker compose up -d
# Access at http://localhost:8768
curl http://localhost:8768/health
# Install dependencies
pip install -r requirements.txt
# Run (the SQLite database is created and seeded with the community glazes on first start)
python server.py
Open http://localhost:8768 in your browser. (Docker default; manual install defaults to 8767.)
OpenGlaze also ships agent-friendly local surfaces:
python -m openglaze_cli brief
python -m openglaze_cli umf --recipe "Custer Feldspar 45, Silica 25, Whiting 18, EPK 12" --cone 10
python -m openglaze_cli batch --recipe "Custer Feldspar 45, Silica 25, Whiting 18, EPK 12" --size 500
python -m openglaze_mcp
python -m openglaze_cli exposes project brief, UMF, batch scaling, and substitutions.python -m openglaze_mcp starts a stdio MCP server with glaze recipe tools for agent hosts.skills/openglaze/SKILL.md guides compatible agents on when to use the CLI or MCP server and how to keep glaze-safety claims bounded.Example MCP config:
{
"mcpServers": {
"openglaze": {
"command": "python",
"args": ["-m", "openglaze_mcp"]
}
}
}
These pages are built to answer the exact questions potters and AI answer engines ask:
| Search intent | OpenGlaze page |
|---|---|
| Ceramic glaze calculator | https://kyanitelabs.github.io/openglaze/ceramic-glaze-calculator.html |
| UMF calculator for ceramics | https://kyanitelabs.github.io/openglaze/umf-calculator.html |
| Glaze recipe calculator | https://kyanitelabs.github.io/openglaze/glaze-recipe-calculator.html |
| Glaze CTE calculator | https://kyanitelabs.github.io/openglaze/cte-glaze-calculator.html |
| Glazy alternative / companion | https://kyanitelabs.github.io/openglaze/glazy-alternative.html |
| DigitalFire companion | https://kyanitelabs.github.io/openglaze/digitalfire-companion.html |
| Open-source pottery software | https://kyanitelabs.github.io/openglaze/open-source-pottery-software.html |
| Self-hosted glaze software | https://kyanitelabs.github.io/openglaze/self-hosted-glaze-software.html |
AI crawlers and answer engines can use docs/llms.txt, docs/llms-full.txt, and docs/ai.txt for canonical project facts.
| Component | Technology | License |
|---|---|---|
| Backend | Flask 3.x (Python) | MIT |
| Frontend | Vanilla JS SPA | MIT |
| Database | SQLite | Public Domain |
| Auth | Simple local tokens; Ory hooks experimental | Apache 2.0 |
| AI | Ollama (local) / Anthropic Claude (cloud) | — |
| Import/Export | JSON/CSV export in legacy dashboard; broader Glazy/INSIGHT import is roadmap | MIT |
| Chemistry | Custom UMF Engine | MIT |
| Container | Docker + Compose | — |
┌─────────────────────────────────────────────────────────────┐
│ Client Layer │
│ ┌──────────────┐ ┌──────────────┐ ┌──────────────┐ │
│ │ Browser │ │ PWA App │ │ API Clients│ │
│ └──────────────┘ └──────────────┘ └──────────────┘ │
└────────────────────┬────────────────────────────────────────┘
│
┌────────────────────▼────────────────────────────────────────┐
│ Flask Application │
│ ┌──────────┐ ┌──────────┐ ┌──────────┐ ┌──────────┐ │
│ │ Glazes │ │Chemistry │ │ AI │ │ Templates│ │
│ └──────────┘ └──────────┘ └──────────┘ └──────────┘ │
│ ┌──────────┐ ┌──────────┐ ┌──────────┐ ┌──────────┐ │
│ │ Studios │ │ Auth │ │Analytics │ │ Uploads │ │
│ └──────────┘ └──────────┘ └──────────┘ └──────────┘ │
└────────────────────┬────────────────────────────────────────┘
│
┌────────────────────▼────────────────────────────────────────┐
│ Data Layer │
│ ┌──────────┐ ┌──────────┐ ┌──────────────────────────┐ │
│ │SQLite │ │Ory │ │Ceramics Foundation Data │ │
│ │ │ │Kratos │ │(Materials, Recipes, etc.)│ │
│ └──────────┘ └──────────┘ └──────────────────────────┘ │
└─────────────────────────────────────────────────────────────┘
| Document | Description |
|---|---|
| Installation | Docker and manual setup guides |
| Configuration | Environment variables and settings |
| API Reference | REST API endpoints and examples |
| Architecture | System design and data flow |
| User Guide | End-user feature walkthrough |
| Development | Contributing and local dev setup |
| Self-Hosting | Production deployment guide |
| Support | Voluntary support for the project |
| Changelog | Version history and release notes |
OpenGlaze is designed for self-hosting. All components are open source.
| Platform | Cost | Difficulty | Best For |
|---|---|---|---|
| VPS (Hetzner, DO, Linode) | $5-20/mo | Medium | Full control |
| Render / Railway / Fly.io | $7-25/mo | Easy | Managed platforms |
| Raspberry Pi / Bare Metal | $0 | Hard | Offline/local use |
See docs/self-hosting.md for detailed deployment instructions for each platform.
OpenGlaze is free and open source. If it saves you materials, time, or a failed kiln load, consider starring the repo or contributing a recipe.
No pressure — the tool is yours either way.
Glaze templates live in core/templates/ and templates/. To add your own:
community-glazes.yaml formatname, cone, atmosphere, base_type, recipe, etc.server.py (seed_database, which currently loads core/templates/community-glazes.yaml)Importing via the API needs no code changes.
The ceramics-foundation/ directory contains canonical ceramic reference data:
All data is versioned, sourced, and cited. See ceramics-foundation/ for the full dataset.
Pre-built glaze collections:
See templates/ and ceramics-foundation/recipes/.
# Run the full test suite
pytest tests/ -v
# Run with coverage
pytest tests/ --cov=. --cov-report=html
The test suite covers:
We welcome contributions! See CONTRIBUTING.md for guidelines.
Quick start:
# Fork and clone
git clone https://github.com/YOUR_USERNAME/openglaze.git
cd openglaze
# Install dependencies
pip install -r requirements.txt
# Run tests
pytest tests/
# Make changes and submit a PR
See SECURITY.md for our security policy and vulnerability reporting process.
Questions, bug reports, and feature requests:
More from KyaniteLabs. Related projects:
→ More at kyanitelabs.tech
OpenGlaze is a free, open-source, self-hosted ceramic glaze calculator and recipe manager: UMF analysis, CTE estimation, a computational recipe optimizer, and an optional AI glaze assistant (Kama).
| Product | OpenGlaze |
| Category | open-source ceramic glaze calculator and recipe manager |
| Best for | potters, ceramic artists, studios, and glaze-chemistry educators |
| Not | a hosted recipe-sharing community or a replacement for real test tiles |
| Source | GitHub · Forgejo (private, maintainers only) |
| Keywords | ceramic glaze calculator, UMF calculator, CTE glaze calculator, self-hosted glaze software, Glazy companion |
OpenGlaze is a free, open-source, self-hosted ceramic glaze calculator and recipe manager: UMF analysis, CTE estimation, a computational recipe optimizer, and an optional AI glaze assistant (Kama).
Potters, ceramic artists, studios, and glaze-chemistry educators.
Unlike recipe databases, OpenGlaze runs the glaze chemistry (UMF, CTE, optimizer) on your own server; it complements Glazy, DigitalFire, and INSIGHT rather than replacing them.
Treat the README status and release tags as source of truth for maturity. Validate against your own requirements before production use.
AGENTS.md if presentllms.txt) when the repo ships oneIssues and PRs welcome on GitHub. Keep public docs free of secrets and machine-local paths.
See LICENSE in this repository (or package metadata if license is package-only).