A read-only visual demo of the neural-lam knowledge graph. The graph is pre-built locally and committed to the repo — no indexing happens at runtime, so the free tier has plenty of CPU headroom.
From your neural-lam root:
python consequencegraph/cli.py index ./neural_lam --preset neural_lamThis writes .consequencegraph/cache.json. Now copy it into the consequencegraph repo:
mkdir -p consequencegraph/neural_lam_cached
cp .consequencegraph/cache.json consequencegraph/neural_lam_cached/cache.jsonThe server in production mode loads from this cache on startup. No network calls, no indexing, instant boot.
In server.py, the main() function defaults --path to ./neural_lam.
For deployment, point it at the cached directory:
parser.add_argument("--path", default="./neural_lam_cached")Or just set it in render.yaml startCommand (already done).
git add consequencegraph/
git commit -m "add consequencegraph with pre-built neural-lam graph"
git pushMake sure neural_lam_cached/cache.json is NOT in .gitignore.
It's ~2MB, fine to commit.
- Go to https://render.com and sign up (free, no credit card)
- New → Web Service → Connect your GitHub repo
- Render will detect
render.yamlautomatically - Deploy
Your URL will be: https://consequencegraph.onrender.com (or similar)
/api/reindexis disabled (returns 403)- Rate limit: 60 requests/minute per IP
- CORS open (anyone can embed the API)
- Free tier sleeps after 15min inactivity — first load after sleep takes ~30s
To avoid sleep on the free tier, use UptimeRobot (free) to ping /api/stats
every 14 minutes.
# Full mode — indexes live codebase, reindex enabled
python consequencegraph/server.py --path ./neural_lam --preset neural_lam --reindex
# Production simulation locally
CONSEQUENCEGRAPH_ENV=production python consequencegraph/server.py --path ./neural_lam_cached