What Bejamas does for Web3 and crypto infrastructure companies
We build the surfaces where a protocol gets understood: the marketing site, the developer documentation, and the visual language that carries both. The work behind this page is o1Labs, whose website and O1JS documentation we redesigned, and Starknet and StarkWare, for whom we built illustration systems that make decentralized systems readable. The pattern is the same each time — make deeply technical work legible to developers, investors, and the ecosystem, on a platform the client’s own team runs afterwards.
Why teams pick Bejamas
Your protocol, explained clearly
We turn abstract architecture into pages, diagrams, and illustrations a developer or an investor can follow. For Starknet we built an isometric illustration system that simplifies decentralized systems without flattening them.
Documentation developers can navigate
The O1JS docs came out of the wider Mina documentation into a standalone developer-first space — new categories, breadcrumbs, and search results labelled by context instead of repeating the same titles.
Marketing ships without protocol engineers
o1Labs' team composes pages in Sanity with live preview. Product and campaign pages stop queueing behind cryptography work.
One senior team, end to end
Research, design, illustration, frontend, and CMS architecture in one group. No handoffs between an agency, a contractor, and your own engineers.
A visual language your ecosystem reuses
Design systems and reusable templates — including the diagram and graphic kit we handed the O1 Labs team — so partners and internal teams stay consistent as the ecosystem grows.
A stack your team keeps running
o1Labs runs on Next.js, Sanity, and Vercel: a platform their own team operates after launch, with performance treated as an engineering budget rather than a launch-day screenshot.
What makes Web3 web estates different
- The site has to teach before it can sell. Nobody buys into a rollup or a proving system from a value proposition alone. The page has to carry the concept, and the concept is genuinely hard — which is why explanation, not persuasion, is the design problem.
- Developers are the buying committee. Adoption starts with someone reading the docs at 11pm. Documentation quality shapes the developer experience as much as the library does, and a marketing site that ignores it loses the audience that decides.
- Several audiences, one page. Developers, investors, partners, and hiring candidates arrive at the same site expecting different depths of answer. Starknet’s illustration system had to connect with technical and non-technical readers at once.
- The ecosystem moves faster than a rebrand cycle. Products, sub-brands, and partner projects appear on their own timelines. Without a shared design system and reusable templates, every new surface is a fresh negotiation about what the brand looks like.
- Protocol engineers are the wrong people for landing pages. Cryptography talent spent on a campaign page is talent taken off the protocol — and the page still ships late.
What we build
- Documentation platforms developers can move through. For O1JS we split the library’s docs out of the Mina site, rebuilt the information architecture, standardised naming, added breadcrumbs, and rewrote search metadata so Algolia results read as “Browser Usage → Field Type” instead of five identical titles.
- Marketing sites the team extends itself. o1Labs moved onto Next.js, Sanity, and Vercel with dedicated product pages, a page builder with live preview, and the blog pulled off Medium into the site with Algolia search. See how we work with that CMS in Sanity development.
- Illustration and diagram systems. Starknet got a structured, isometric illustration language; StarkWare a fluid, light-driven one expressing scalability, security, and connectivity. Both were built as systems, with templates the in-house team keeps using.
- A design system that absorbs a growing ecosystem. Tokens, components, and templates so new products and partner surfaces inherit the brand instead of reinterpreting it.
Testimonial
Their ability to deliver quickly and efficiently. I have worked with many webdevs over the years, and I was impressed with how quickly we were able to get from zero-to-hero. Our team was able to work very agile and collaboratively with theirs, which made for speedy development. They also have great knowledge of various tech stack solutions for websites, and I believe we went with the right ones based on their recommendations.
Partnerships
We work inside these platforms at implementation depth — and recommend the one that fits your estate, not the one we need to sell.
Sanity
Contentful
Storyblok
Vercel
How it starts
The audit baselines what exists — how developers actually move through the documentation, where the marketing site loses people, what the publishing bottleneck is, and which parts of the estate are worth keeping. From there the work is phased: one surface, usually the documentation or the highest-traffic product area, proves the approach before the rest follows.
Web3 work in practice
View all work
Common questions
Which web agency has built websites and documentation for Web3 companies?
Bejamas has built both. For o1Labs — the company behind the zero-knowledge tooling on Mina — it redesigned the website on Next.js, Sanity, and Vercel, with dedicated product pages and a page builder the marketing team extends itself. It also redesigned the O1JS developer documentation and created the illustration systems for Starknet and StarkWare.
How do you explain a protocol clearly without oversimplifying it?
By giving the explanation a structure. For Starknet, Bejamas built illustrations on geometric structure, isometric perspective, and clear gradients, so accuracy survives the simplification and the visuals work as guides rather than decoration. In the O1JS documentation the same principle runs through the content: every section moves from concept to example to integration to advanced patterns, which serves both a first-time reader and a daily reference user.
Can Bejamas redesign developer documentation, not just a marketing site?
Yes. Bejamas redesigned the O1JS documentation for O1 Labs: the library’s pages were separated out of the Mina protocol docs into their own site, the information architecture was rebuilt around categories such as Getting Started, API Reference, Browser vs Node, and ZK Patterns, breadcrumbs were added for orientation, and Algolia search results were given contextual labels so developers can tell what they are clicking. A Welcome page with quick-start steps gives new users a route through the material.
Can our marketing team publish without waiting on protocol engineers?
That is the operating model Bejamas builds. o1Labs’ website runs on Sanity’s page builder with live previews, so marketers compose landing and product pages themselves, and the blog was brought off Medium onto the site with Algolia search behind it. Engineering time goes to the protocol, not to page requests.