Ackvia.
Reliable form delivery.
With retries, state and visibility.
Ackvia accepts website form submissions, stores them, and delivers them to configured destinations. The project is evolving from a simple “receive and notify” MVP into a delivery system with background workers, attempts, retries, explicit statuses, locking, and auditability.
Current focus: making delivery behavior observable and reliable.
A closer look Implementation, boundaries & current direction
What I built
Async FastAPI endpoints, PostgreSQL persistence, Telegram delivery, a separate background worker, delivery attempts, retry scheduling, and explicit delivery states including PENDING, PROCESSING, AWAITING_RETRY, SUCCEEDED, FAILED, and UNKNOWN.
What I’m learning
How external side effects change backend design: claiming work safely, separating API latency from delivery latency, tracking attempts, testing failure paths, and designing the database around real worker queries.
Where it’s going
Ackvia is now also my university thesis project. The immediate goal is to turn the current backend into a finished product that outside users can connect to their forms and trust.