Unibase builds open infrastructure for AI agents. The work started from one problem: an agent that cannot remember anything between sessions has to be told everything again, and an agent that cannot pay for what it uses has to wait for a person. We build the pieces that fix each of those, and we publish them so they can be used separately.
Four parts, each usable on its own. None of them requires the others to be useful, and none of them is a closed service you cannot inspect.
The network itself runs on UB, which is what nodes stake, what fees are priced in, and — once locked as vUB — what governance counts.
Membase is the memory product, and it is made by Unibase. It has its own site at membase.com because it is the part most people use directly — the web app, the Chrome extension, the desktop app and the API behind them. Unibase is the company and the rest of the infrastructure.
So: the same people, two names, used for different things. If you are here about your own memory, Membase is the product. If you are here about agent identity, payments or storage, those live on this site.
The protocols, SDKs and contracts are published on GitHub, and the documentation is at docs.unibase.com. The UB token contract was audited by PeckShield and the report is published in full, alongside the deployed addresses on the token page. What ships, and when, is on the changelog.
Write to support@unibase.com — support, press, partnerships, and anything about an account. It is read by the team, not by a form.
Day to day we are on X and in the community channels linked at the bottom of every page. For how something works, the documentation is usually faster than we are, and the blog is where we write things up at length.