With this update, many things have changed and improved. I recommend trying out the advanced settings. Please visit the docs page for a more detailed overview. Thank you for supporting DASCA. Removed (1)
I m working on the next update for Proximity Lock, and I want to sanity-check the direction with the PH community.
Right now, the product is mainly used by technical users who are comfortable installing and configuring things themselves. But after talking to a few early users, one pattern stood out:
Non-technical users like the idea, but hesitate because setup feels too technical.
So the next update I m planning is a simple tray app:
We support flexible compute sizing in Bult.ai so apps only use what they actually need.
XS to XL sizes cover everything from prototypes to databases, with per-minute billing and the ability to resize anytime from the Canvas UI. Compute options: XS: 0.1 vCPU, 256 MB RAM, $2.7 per month. Ideal for prototypes S: 0.25 vCPU, 512 MB RAM, $5.4 per month. Suitable for small apps M: 0.5 vCPU, 1 GB RAM, $12 per month. Designed for web applications L: 1 vCPU, 2 GB RAM, $24 per month. A good fit for APIs XL: 2 vCPU, 4 GB RAM, $48 per month. Optimized for databases
Custom sizes are also available for advanced workloads available on request. Happy to answer questions about sizing or use cases.
I m curious how people here think about a calmer, signal-first feed in practice.
If you ve tried Trace already: What felt immediately useful? What felt missing or confusing? What would make it something you d actually open every day?
If you haven t tried it: What would you need to see before giving a feed like this a real shot? What would make you bounce?
I m early and still shaping this, so honest feedback (good or bad) is genuinely helpful.
