Onlys: investor cabinet, frontend and backend
Client:
Onlys, tokens for AI influencer projects
Segment:
Web3, AI influencers
Result:
Cabinet and API live
Direction:
Web service development
Stack:
React, Node.js, Fastify, Docker
The task
Onlys issues tokens for projects built around AI influencers: holders receive a share of the project’s revenue. The onlys.fun landing was live, but investors had no personal cabinet.
They needed a cabinet where an investor signs in without a password, picks a project, buys tokens and sees the portfolio and payouts. The design had to continue the landing, and the data had to come from their own backend.
What we did
- Designed the frontend on Feature-Sliced Design: pages, widgets, user actions and entities live in separate layers, so a new section is added without touching the old ones.
- Built the cabinet on React 18 and Vite: a project catalog with filters, a presale section, a project page with a gallery and a raise progress bar, and a payouts section with a monthly chart and CSV export.
- Carried the landing’s style into the cabinet: fonts, the lime accent, Framer Motion animations. Charts are drawn in SVG, with no heavy libraries.
- Converted the photos to WebP: the cabinet’s images went from 9.3 to 0.3 MB.
- Wrote the backend on Node.js and Fastify: an API for the catalog, the portfolio and payout history at api.onlys.fun.
- Added Google sign-in: the cabinet asks for no password and stores only the email and public name, and the session lives in a secure cookie.
- Connected token purchases: the cabinet issues an invoice and sends the investor to the payment page.
- Set up deployment: Docker and Traefik on the server, and GitHub Actions ships every push to the main branch.
Outcome
The cabinet runs at app.onlys.fun and the API at api.onlys.fun. An investor signs in with Google, picks a project, pays for tokens and sees the portfolio and payouts in one place.
The frontend and backend are separate: new projects and data arrive through the API without rebuilding the interface, and updates ship on their own after a push to the repository.
