Loading DEV/STATION…
One developer.
A growing community.
DEV/STATION is built and maintained by Jhet Tacalig to help developers share their work, find inspiration and exchange useful feedback.
DEV/STATION is an independent community project, rather than a company-backed platform. Building features is one part of the work. Keeping accounts working, reviewing submissions, fixing issues and maintaining the infrastructure all take time.
As more developers join, the goal is to grow the platform thoughtfully: keep browsing responsive, protect account access and make useful features easier to reach.
Meet Jhet TacaligDEV/STATION uses a hybrid setup. Each service has a specific job, so public browsing, account data and community conversations don’t all rely on the same backend.
Eligible cached responses can return here. Account actions and origin requests continue to the application.
A simplified view of the website. Sign-in uses Supabase Auth; selected features also connect directly to public Cloudflare services. Private data is kept separate from public catalogue snapshots.
Delivers approved portfolio images from R2 and public catalogue snapshots near visitors. Workers handle selected background jobs and community services.
Reusable public responses help reduce repeated requests to the application and database.
Hosts the Next.js website and server APIs. The application checks requests and permissions before carrying out protected actions or connecting to a backend.
Application functions are configured in Singapore, close to the primary database and AWS forum backend.
Manages sign-in and core community records, including portfolios, public profiles, projects and portfolio ratings. Access policies separate public browsing from private account data.
Profiles and portfolio records share the same identity system, so members can use one account across the site.
API Gateway, Lambda and DynamoDB serve forum discussions and reviews about the DEV/STATION experience. Protected requests are authorized by the website before reaching this backend.
Community conversations have a dedicated backend while staying connected to the existing member accounts.
Public content can be cached; private account actions still need authorization. The setup uses permission checks, database access policies and signed service requests where appropriate. Background jobs help move suitable work out of the browsing experience.
These choices help manage load and usage. They don’t remove provider limits or guarantee uninterrupted service. The architecture will keep evolving as the community grows.
We’re looking for supporters and partners who believe in giving developers a place to share their work. Help can be practical, technical or community-led.
Help with domain renewals, hosting, image delivery and the services that keep the site running.
Help investigate bugs, improve accessibility, test features or maintain clear documentation.
Connect a school, developer group or organization with learning opportunities and community activities.
No account needed. Share how you’d like to help through the contact page.