Extremely Important Alpha Disclaimer

Pigbak is in very early alpha. And by “very early alpha,” we mean somewhere in the beautiful and chaotic space between “ambitious concept” and “held together with determination, caffeine, and questionable life choices.”

This software is unfinished. It is experimental. It is under active development. It may work perfectly for five minutes straight and then immediately forget what year it is. Features may appear, disappear, reappear in a slightly worse mood, or behave in ways that suggest they have become self-aware but only in a deeply inconvenient sense.

Also, the name Pigbak may or may not be permanent. I love it. I hate it. It is both excellent and terrible. At this stage, you may as well consider it a code name unless it sticks. It might survive. It might not. Much like certain features, its long-term future remains gloriously uncertain.

By using Pigbak, you acknowledge and enthusiastically accept that:

Things may be broken.
Things may become broken.
Things that seemed fixed may become broken again.
Entirely new and creative forms of brokenness may be discovered.
Buttons may do nothing.
Buttons may do the wrong thing.
Buttons may do the right thing, but in a way that feels suspicious.
Data may save correctly, incorrectly, temporarily, spiritually, or not at all.
Pages may load quickly, slowly, upside down, or with the digital equivalent of a shrug.

Pigbak is not polished software. It is not mature software. It is not enterprise software. It is not “mission critical infrastructure.” It is not something you should rely on for any purpose involving deadlines, money, safety, professional reputation, emotional stability, or impressing someone important.

You should assume at all times that Pigbak may:

contain bugs,
contain weird bugs,
contain bugs that cancel out other bugs,
contain bugs nobody has ever seen before,
and contain at least one bug that will only happen to you specifically, at the worst possible moment, for reasons no one can explain.

There are no guarantees. Not express guarantees, not implied guarantees, not “kind of sounded like a guarantee in the Discord,” not “I assumed it would work because the button looked confident” guarantees. None. Zero. Absolutely no promises are made regarding uptime, reliability, availability, accuracy, compatibility, fitness for a particular purpose, merchantability, or whether the software will do the thing you very reasonably hoped it would do.

Pigbak may crash. It may stall. It may timeout. It may duplicate something. It may delete something. It may incorrectly sort, rank, label, format, cache, sync, export, import, calculate, render, or otherwise interpret your data. It may send you down a baffling rabbit hole of user experience decisions that made sense to someone at some point, probably late at night.

Any feature described anywhere on the site, in documentation, in a roadmap, in a post, in a message, in a changelog, in a tweet, in a dream, or verbally by an overly optimistic founder should be understood as aspirational rather than guaranteed. Just because something exists today does not mean it will exist tomorrow. Just because something is on the roadmap does not mean it is coming soon. Just because something is called a “feature” does not necessarily mean it currently functions as one.

You should back up your data. Then back it up again. Then consider taking a screenshot just in case. If Pigbak stores something important to you, you should behave as though a raccoon with a loose understanding of databases is currently in partial control of the storage layer.

Do not use Pigbak as your sole system of record for anything important. Do not use it where failure could cause financial loss, legal trouble, missed opportunities, ruined trips, broken workflows, damaged relationships, professional embarrassment, or any sentence beginning with, “Wait, why did it do that?” If you choose to do any of those things anyway, that is a bold personal decision and entirely your responsibility.

You also acknowledge that alpha software is, by its nature, a living and shifting beast. The interface may change without notice. Features may be renamed. Workflows may be rearranged. Settings may move to places that feel philosophically wrong. We may fix a bug and accidentally create two more with stronger personalities. We may deploy updates that improve things dramatically. We may deploy updates that make you briefly question reality. This is all part of the thrilling early-access experience.

By continuing to use Pigbak, you confirm that you understand this is an unfinished product being tested in the real world by real people with real browsers, real devices, real expectations, and unfortunately very real edge cases. You agree to approach the experience with curiosity, resilience, and a healthy sense of humor.

In summary:

Pigbak is early.
Pigbak is experimental.
Pigbak may break.
Pigbak may not even keep this name.
Pigbak owes you no miracles.
And there are absolutely no guarantees.

Use accordingly.