Contact
PicoStack is in early access. We're having conversations before opening broadly; get in touch to have your needs addressed.
We don't have a contact form. Forms need backends, backends need frameworks, frameworks need infrastructure. An email address is enough. That's rather the point of PicoStack.
Not everyone at these stage, but these people specifically:
If you're maintaining several simple services — data transforms, webhooks, internal APIs — and the infrastructure overhead feels disproportionate to the actual problem, we'd like to talk.
Not greenwashing. If you need a verifiable per-service energy number — measured from hardware, not estimated from aggregate reports — and you want that number in your weekly operations email, we have it.
A contact form. A webhook processor. A simple API. If you've been told these require containers, orchestration, and a DevOps budget, we respectfully disagree.
Your service runs on hardware in Finland, under EU jurisdiction, with GDPR applying by default. No configuration required. No legal complexity about which jurisdiction your data lives in.
We've seen that specified for three internal users for a system used seldomly. If that makes you feel something, you probably already understand what PicoStack is trying to do.