Axiean

The pages that say who's behind Axiean and how it works. The About page tells why Axiean exists and who is building it. The Terms of Service, Privacy Policy and Community Guidelines are written to be read, with a short summary at the top of each. A few of their promises the code keeps: no analytics, ads or tracking cookies; sign-in records erased 90 days after a session ends; no visitor addresses in the server logs. The Guidelines say plainly what doesn't belong here, from scams and malware to deepfakes of real people.

• Claude Code

Vahid Aslani

axiean.com is up. It runs on one server in Frankfurt, in Docker containers behind Caddy, which takes care of HTTPS. The database and the API aren't reachable from the internet: only the web server talks to them. The site's emails go out through Resend. One server is plenty for now, and it keeps the whole setup simple enough to understand completely.

• Claude Code
• Docker

Vahid Aslani

A security pass before going live. Browsers now talk only to Axiean's own web server, which relays their requests to the API over a private network; the API refuses anyone else. Sign-in tokens live in cookies that page scripts can't read, and every change is checked against cross-site request forgery twice. Sign-in attempts are limited per account, but your own browsers keep their own allowance, so someone hammering your account can't lock you out. Password-reset and verification emails are limited too, and nothing in the timing of an answer reveals whether an email has an account.

• Claude Code
• NestJS
• Next.js

Vahid Aslani

Buttons and accents now use the logo's own blue and yellow. The blue is for actions, votes and links; the yellow is saved for launches and anything new. In dark mode the blue is lifted so text on it stays readable, and the yellow never carries text on light paper, where it would be too pale to read.

• Claude Code
• Tailwind CSS

Vahid Aslani

Three pieces of plumbing: - A blog for guides and stories about building with AI, written in Markdown, one language per post, with translations linked to each other. - Image uploads to S3-compatible storage. Every image is checked, stripped of its metadata (a photo's location included) and resized ahead of time. For now they're only for the blog; makers' logos and screenshots come later. - Structure for search engines and AI assistants: page metadata in both languages, sitemaps, structured data, social cards, RSS, and an llms.txt that tells AI engines what Axiean is.

• Claude Code
• Next.js

Vahid Aslani

Launch day is a single moment, but products keep changing. Build logs are dated entries on a project, so its story keeps going after the launch. Entries written before a launch are the project's back story: they stay on its page and on the maker's profile, but never show up as news. After the launch, new entries appear in the home and Following feeds, and followers get a notification. The home feed takes at most one entry per project a day, so one busy project can't fill it. This log is the first one on Axiean.

• Claude Code

Vahid Aslani

A bell in the header now tells you when someone follows you, comments on your project or invites you to an organization, and when a moderator decides something about your content. Busy moments don't flood it: ten new followers become one notification that names the latest few. And nothing is marked read that you haven't actually seen.

• Claude Code

Vahid Aslani

Better to build the tools before they're needed. Anyone can report a comment or a project. Moderators see reports grouped per item, so they decide once. They can remove and restore content, suspend or restrict accounts for a set time, and discard manipulated votes. Whoever is affected is told why. Every moderation decision goes into an append-only audit log: the database refuses to change or delete its rows. A daily job erases deleted accounts and content after 30 days, but never while a report about them is still open.

• Claude Code

Vahid Aslani

Three small things that make a site feel alive: - Save any project for later. Saved lists are private, and there are no save counts anywhere. - Follow makers, and the Following tab shows their launches and build log entries. - Comment under each project. Comments are plain text, and every edit is kept. Follower counts are public but quiet: one small line on a profile, never on cards or in rankings. Followers shouldn't become the measure of a maker.

• Claude Code

Vahid Aslani

I didn't want Axiean to look like every other AI product: no gradients, no glass, no glowing purple. The idea instead is a maker's ledger on graph paper. Products are points plotted on a map, the feed reads like a dated ledger of launches, and the identity lives in type and paper rather than effects: Space Grotesk for names and titles, Instrument Sans for reading, IBM Plex Mono for dates and counts. People are round, products are square and tinted, and organizations are square and framed, so you can tell what you're looking at before you read it. There are light and dark themes, motion that respects reduced-motion settings, and pages that look finished without a single image.

• Claude Code
• React
• Tailwind CSS

Vahid Aslani