buildCOMMUNITY BUILDS
Show the system you built.
Share exact parts, your workload and photos you have permission to use. Every public build and comment requires moderation.
Completed systems are owner-attested. BuildAPC has not independently verified ownership, completion or performance.
Checking community availability. This local static preview may not include account services.
Approved completed builds
Your private drafts and submissions
Drafts and photos are private until an explicitly configured moderator approves a reviewed snapshot and public publishing is enabled. Editing an approved build withdraws it immediately and requires fresh review.
Your comments
Your private reports
Feedback lists and exports contain at most20comments and20reports per page. Next-page controls retrieve the remaining pages; build exports include all active drafts and their bounded submission history.
Prepare a technical copy
Read the current browser draft or a BuildAPC build JSON locally. Private notes, names from the builder, prices, budgets, custom items, installation assumptions and shopping/account details are excluded. Only the chosen fields and exact part list below go to community storage after your review.
This does not change the builder or private cloud library. Community copies are separate. Nothing uploads automatically.
The community copy
Review every field below. These are the fields and exact component identities you are choosing to share; source-bound labels and moderation state accompany them. Photos require a separate preview and rights confirmation.
Moderation queue
Review the exact submitted revision, parts, context and photos. A different configured moderator must approve your own submissions. Approving is unavailable while launch policy is locked.
Your control over community data
At most ten active drafts, five photos per build and twenty submitted versions per draft. Photos are resized to at most1600×1600 pixels, stripped of metadata and limited to2MiB each. Upload and posting rates are bounded per signed-in account.
Withdrawal removes public visibility. Deleting removes build text, submission versions and associated photo access; object deletion is retried and reported. Minimal hashed ownership, revision, deletion and photo-key records remain to prevent stale uploads from restoring removed data and to retry cleanup. Downloaded or copied material is separate.
Community data is separate from the private cloud build library. Read the storage details →
Erase my community data
This removes your community build text, submission history, photos and your authored comments/report details. Browser drafts, downloads and the private cloud library are kept.