puemos
Craftplan - Open-source production management for small manufacturers
My wife was planning to open a micro-bakery and we started looking at software to manage recipes, inventory, orders, and production. Everything was either expensive, too generic, or both. The workflows for a small-batch manufacturer aren’t that complex, but the pricing acts like they are.
So I built Craftplan. All the features were tailored to what she actually needed, and I figured other small-scale manufacturers (soap makers, breweries, candle makers, etc.) probably need the same things. So I’m putting it out there for free.
- Live demo: https://craftplan.fly.dev (
test@test.com/Aa123123123123) - GitHub: https://github.com/puemos/craftplan
- Docs: https://puemos.github.io/craftplan
- Self-hosting guide: https://puemos.github.io/craftplan/docs/self-hosting/
What it does:
- Product catalog with versioned recipes (BOMs) and automatic cost rollups across materials, labor, and overhead
- Inventory tracking with lot traceability, expiry dates, allergen/nutrition flags, and demand forecasting
- Order processing with calendar-based scheduling and allocation to production batches
- Production planner with make sheets, material consumption from specific lots, and cost snapshots
- Purchase orders with receiving workflow that auto-creates inventory lots
- Basic CRM for customers and suppliers
- CSV import/export, iCal calendar feed, JSON:API and GraphQL endpoints
Experience building with Elixir, Ash and Liveview
- Speed: you get to test and improve things sooo fast. The DSL makes it simple to translate your thinking into live product
- Extensibility: With Ash + LiveView you can add more features so easily. Adding JSON:API + Grapghql was a few minutes.
- UX: I believe LiveView makes it simple to deliver great UX since it forcing you to keep things simple with no so much interaction overhead which most of the time means better and simple experience
Self-hosting:
Docker image: ghcr.io/puemos/craftplan (amd64 + arm64)
Docker Compose bundles PostgreSQL 16 + MinIO.
curl -O https://raw.githubusercontent.com/puemos/craftplan/main/docker-compose.yml
curl -O https://raw.githubusercontent.com/puemos/craftplan/main/.env.example
cp .env.example .env
docker compose up -d
Other details:
- Email config from UI (SMTP, SendGrid, Mailgun, Postmark, Brevo, Amazon SES)
- API keys encrypted at rest (AES-256-GCM)
- Role-based access (admin/staff)
- Tech stack: Elixir, Ash Framework, Phoenix LiveView, PostgreSQL
- License: AGPLv3
Feedback welcome (and needed!)
Most Liked
code-shoily
This looks fantastic. The UI is
. Will take a look at the code later today, hope there’d be a lot for me to learn from! Thank you for building and sharing this.
puemos
Feel free to ask anything, will be happy to share ![]()
FlyingNoodle
Since you wrote that you welcome feedback. Doing this in a LiveView is not recommended in ash:
Ash.read!(Craftplan.CRM.Customer,
actor: socket.assigns[:current_user],
load: [:billing_address, :shipping_address, :full_name]
)
Instead, you should define idiomatic actions on your resources and domains: Actions — ash v3.29.3
So in this case I would use the Ash action that you already have defined in your domain:
Craftplan.CRM.list_customers!(actor: socket.assigns.current_user, load: [:billing_address, :shipping_address, :full_name])
Popular in Discussions
Other popular topics
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #channels
- #elixirconf
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #phoenix_html
- #iex
- #blog-post
- #graphql
- #genstage
- #ai
- #websockets
- #supervisor
- #advent-of-code
- #elixirconf-us
- #distillery
- #processes
- #forms
- #api
- #metaprogramming
- #security
- #performance









