Commons
v1 ⇄ v2 — one iteration apart
A paid community with Stripe supporter subscriptions — then one iteration adds AI moderation without touching the billing.
What was asked for
This is the specification the app was generated from — one prompt, published in full and unedited, rather than a summary of it.
Build an image-sharing community app with a paid supporter tier. Users register with email and password, log in, and create a profile with a display name, a short bio, and an avatar image they can upload. Users create posts that consist of an uploaded photo and a caption. There is a home feed that shows posts from the people the user follows, and a separate discover feed that shows recent posts from everyone. Users can like a post and leave comments on a post. Users can follow and unfollow other users. Opening a user's profile shows their posts, their follower count, and a follow button. Users can become supporters by subscribing to a monthly supporter plan through a secure hosted checkout page. A user can mark any of their posts as supporters-only. Supporters-only posts are shown in full only to users with an active supporter subscription; everyone else sees a locked placeholder instead of the photo. A user can cancel their subscription from a billing page, and when the subscription ends their supporter access ends with it. There is a site operator (admin) who signs in with operator credentials configured in the environment — there is no admin signup page. The admin has a dashboard that shows recent posts and members and lets the admin remove a post. A user gets a notification when someone likes their post, comments on their post, or follows them.
What got built
- Stripe subscriptions
- Admin dashboard
- Social feed
- Media
- v2 adds: AI moderation
Things you can actually do in it
The app is live and public. Without taking our word for anything, you can:
- Subscribe with the Stripe test card — a locked supporters-only post unlocks
- On v2, try posting abusive text — it’s blocked with a written reason
- Open the admin moderation queue: every flagged item with the AI’s rationale
- Compare v1 and v2 — the Subscribing concept and the Stripe utility are byte-for-byte identical
The code
The repositories are public: a Deno backend carrying the generated test suite, the OpenAPI spec and a Dockerfile, and a React frontend built against that same spec. This is the export a build hands you — clone it and read it.
Every one of them has exactly one commit: "Initial export from ConceptualAI". Nothing has been hand-fixed after the fact, and you do not have to take our word for that — the commit history is public, and a second commit would be sitting right there if we had.
Why this one is here
It has a real backend
Authentication, persisted data, and the integrations above are running server-side against a real database — not mocked, and not a frontend pretending.
Its tests are in the repository
The concepts underneath — data, auth, the state everything else depends on — are accepted only once their generated tests pass against a real database. Those tests shipped with the code, so you can run them yourself.
It runs without us
No proprietary runtime and no SDK in between. Clone the backend and it runs anywhere a container runs.
You would own this one
An equivalent build hands you both repositories on any plan — Free included, once you have the three credits a minimum build costs. See pricing.
Build something like this
If this looks like the thing you are trying to build, describe yours in the builder. If it looks like less than what you need, our honest comparison covers when an app builder or a development shop is the better call.