Integrate Clerk and Neon for Orlivo
$15-25 USD / hour
Posted 1 minute ago
•
Ends in 6 days
$15-25 USD / hour
Full-Stack Developer for EdTech Platform Integration | Clerk, Neon PostgreSQL and GitHub Project description We are building Orlivo, a Swedish education platform that helps students with reading, writing and planning, and gives school staff tools to organise support and reduce administration. Orlivo consists of several existing applications with separate GitHub repositories. Orlivo Admin & Core is the shared backend for identity, school memberships, roles, permissions and app licences. Orlivo One is the entry point where staff should see the apps they are entitled to use. We are looking for a developer with hands-on experience integrating Clerk authentication with a custom backend and working with Neon PostgreSQL. The first assignment is to review the current implementation and establish a reliable path to connecting Orlivo One to Core in our development environment. Milestone 1 – Paid technical review * Review the relevant GitHub repositories, setup instructions, authentication flow and database migrations. * Trace the flow from a user signing in through Clerk to Core determining the user’s school membership, role and app access. * Check how the backend validates Clerk sessions or tokens and how it handles expired sessions, users linked to multiple schools and Core being unavailable. * Review the Neon development database setup, including existing migrations and the permissions used by the application at runtime. * Deliver a short written report covering what already works, what you verified, what blocks the integration and what you recommend changing. Include a fixed-price proposal and acceptance criteria for the next milestone. Milestone 2 – Implementation, subject to approval * Implement the agreed changes in a separate Git branch and submit a pull request for review. * Demonstrate that a test user can sign in to Orlivo One and see the correct apps for their active school, role and licence. * Verify that a user cannot access another school’s data or an app they are not entitled to use, even by opening a link directly. Verify that access is denied safely if Core is unavailable. * Provide test results and a short handover explaining how to run the integration locally, verify it and roll back the changes if needed. Working arrangements Use the existing codebase and development environment, with synthetic test data and access limited to what the assignment requires. Share proposed database changes for review before applying them. Production access, deployments and merges require separate approval. Written communication and handover can be in English. The applications use Swedish for user-facing text
Project ID: 40828237
About the project
57 proposals
Open for bidding
Remote project
Active 3 secs ago
Place your bid
Bid amount Email addressBenefits of bidding on Freelancer
Set your budget and timeframe
It's free to sign up and bid on jobs
57 freelancers are bidding on average $19 USD/hour for this job


Hi, [[CLERK AUTHENTICATION AND NEON CORE INTEGRATION REVIEW]] — the key is ensuring Orlivo One receives the correct school-specific permissions from Core, with no cross-school access or unsafe fallback when Core is unavailable. I’d start with the paid technical review exactly as outlined. I’ll inspect the relevant repositories, trace Clerk sign-in and token validation through Core, and verify how school memberships, roles, licences, and active-school selection are resolved. I’ll also review Neon migrations, runtime database permissions, and the handling of expired sessions, multiple school memberships, and Core outages. The review will distinguish verified behaviour from assumptions and identify the specific integration blockers. You’ll receive a concise technical report, recommended changes, and a fixed-price proposal with measurable acceptance criteria for Milestone 2. If implementation is approved, I’ll work in a separate Git branch, submit a pull request, and test both authorised access and denial cases, including direct-link attempts, cross-school isolation, and Core unavailability. Database changes will be proposed for review before application, with test results and rollback instructions included in the handover. Could you share the repository structure and local setup instructions so I can identify the exact services involved in the first review? Looking forward to working with you.


Hi, I'm a senior developer with 10+ years of experience building authentication systems and integrations on PostgreSQL, so I understand the architecture you're describing and the security considerations that matter here. I'll start by reviewing your GitHub repositories, tracing the Clerk authentication flow through to Core, and checking how session validation, role-based access and error handling currently work when Core is unavailable or a user belongs to multiple schools. I'll examine your Neon migrations and runtime permissions to identify what's already solid and what needs to change. After that review, I'll deliver a written report with specific findings, a fixed-price proposal for implementation, and clear acceptance criteria so you know exactly what success looks like. For Milestone 2, I'll implement the changes in a branch, verify that test users see only the apps they're entitled to for their active school, confirm that access is properly denied for other schools' data and missing entitlements, and test the fallback behavior when Core is unreachable. I'll provide test results and a short handover covering local setup, verification steps and rollback. I'm available now and will stay on for any questions or adjustments after handover.


Greetings, I see you're looking for a full-stack developer to integrate Clerk authentication with your Orlivo platform, which sounds like a great initiative to support students and school staff. I can help streamline the connection between Orlivo One and Core by reviewing the current setup, particularly focusing on the user authentication flow and database migrations with Neon PostgreSQL. My approach would involve a thorough examination of the existing GitHub repositories, ensuring that the user experience is seamless when signing in and accessing the right applications. I’ll detail any obstacles I find and provide actionable recommendations in a concise report. With my experience in API integration and database management, I am confident I can effectively address the integration challenges you're facing. Best regards, Saba Ehsan


[CLERK + NEON INTEGRATION] Hello! I'm Fernando, a developer from Mexico. Orlivo’s first challenge is not simply connecting Clerk to Neon; it is making sure Core remains the reliable authority for school membership, roles and app licences. I would begin with the paid review you outlined, tracing the complete sign-in and authorization flow across the repositories, checking token validation, multi-school handling, database migrations and runtime permissions. I’d also verify what happens when sessions expire or Core becomes unavailable, rather than assuming the happy path is sufficient. You’ll receive a concise report separating verified behavior from assumptions, identifying blockers and recommending the next implementation milestone with a clear scope and acceptance criteria. If approved, I can work in a separate branch, submit a reviewable PR and provide tests and rollback instructions. I’m comfortable with written communication and an English handover. I’d be glad to help establish a secure, maintainable integration for Orlivo. Best regards, Fernando


I can review and strengthen Orlivo’s Clerk-Core-Neon integration across the relevant GitHub repositories and development environment. For the paid technical review, I will trace the complete sign-in and authorization flow: Clerk session validation, school membership resolution, roles, licences, multi-school behavior, expired sessions, and safe handling when Core is unavailable. I will also inspect Neon migrations, runtime database permissions, and the existing setup instructions. You will receive a concise report separating verified functionality from blockers, risks, and recommended changes, plus a clearly scoped fixed-price proposal and acceptance criteria for the implementation milestone. If approved, I can implement the agreed changes in a separate branch, provide a reviewable pull request, and validate both positive and negative access cases, including direct-link attempts, cross-school isolation, unauthorized apps, and Core outages. I will include reproducible test results and a practical local handover with rollback guidance. I’m comfortable working with synthetic data, limited access, review-first database changes, and English technical communication while preserving Swedish user-facing content.


Hello - Ricardo here from Buenos Aires. "CLERK + NEON INTEGRATION" - you need Orlivo One to show the right apps for each school. Right now, a staff member signs in, but access depends on several connected layers. The risk is mismatched school memberships or permissions that fail silently. So I'd trace Clerk sessions into Core, then verify Neon migrations and runtime permissions. That way, each staff member sees only licensed apps for their active school. I'd also test expired sessions, multiple schools and Core outages before recommending changes. Would it help if I mapped the access flow with a test case for each failure scenario? Bottom line: you get verified findings and clear acceptance criteria before implementation. If you'd like, message me here and I'll review the repositories and authentication flow. Ricardo - Precision in every step. Value in every result.


Hello I would love to help you seamlessly integrate Clerk and Neon PostgreSQL for Orlivo to ensure secure authentication and a robust backend for your EdTech platform. With extensive experience in full-stack development, modern PostgreSQL databases, and secure identity management, I will efficiently connect your distributed GitHub repositories into a unified, high-performance system. How are you currently handling role-based access control across your existing repositories? Best regards, Giáp Văn Hưng


My 7+ years of freelance web development experience make me well suited to review and strengthen the integration between Orlivo One, Core, Clerk and Neon PostgreSQL. I build interactive web applications for desktop, mobile and tablet, with a strong focus on connecting reliable functionality with clear user experiences. For this assignment, I can carefully examine the existing GitHub repositories, authentication flow, migrations and development setup, then document what is working, what remains blocked and what should change before implementation. My full-stack web development background is relevant to tracing sign-in and access behaviour across applications, while my ability to follow instructions, communicate clearly in English and work collaboratively supports the required technical report and handover. I would be glad to take responsibility for the technical review and provide a clear foundation for the next milestone. Choose me to help make Orlivo’s integration dependable, maintainable and safe for its school-based access model.


Hello, After reviewing your project requirements, I fully understand the scope and expectations for integrating Clerk with Orlivo Core using Neon PostgreSQL. I have hands-on experience with Clerk authentication flows, custom backend token validation, and building secure multi-tenant access control in full-stack environments. Your focus on tracing session handling, multi-school membership, and fail-safe behavior when Core is unavailable aligns with authentication and authorization patterns I’ve implemented before. I have a couple of quick questions. • Is the Orlivo Core backend currently using Clerk’s JWT verification middleware, or is there a custom session validation layer in place? • For the development environment, are the Neon database migrations already applied, or should I expect to run them from the repository as part of the review? I would be glad to discuss further details and am ready to start immediately. Looking forward to hearing from you. Best regards, Carlos.


⚠️ If you're not happy, you don’t pay. ⚠️ Hi, Client. Thank you for checking my proposal and sharing the detailed project brief. I can build your EdTech platform integration using Clerk, Neon PostgreSQL, and GitHub, with a robust, scalable, and secure design. I will deliver: • In-depth review of GitHub repositories and authentication flow • Trace user sign-in from Clerk to Core for accurate role and access validation • Assessment of session management, including handling expired sessions and multiple school memberships • Evaluation of Neon PostgreSQL database setup and existing migrations • Comprehensive report detailing findings, integration blocks, and actionable recommendations You will also receive: • Documentation on running the integration locally and rollback procedures I am confident I can execute your vision professionally and efficiently. Looking forward to discussing the timeline and next steps. Best regards, Chirag Pipal


Greetings, I see that you're looking to integrate Clerk authentication with your existing Orlivo platform and connect it to your Core backend. My approach would start with a thorough review of your current setup, including GitHub repositories and authentication flows. I’ll ensure I trace the user journey from signing in through Clerk to accessing their appropriate roles and permissions in Core. With my experience in PostgreSQL and API integrations, I can identify any blocks in the current implementation and recommend practical changes to streamline the integration. I have a solid understanding of session management and can verify user access rules effectively. I’m excited about the opportunity to contribute to Orlivo and help enhance the experience for both students and school staff. Best regards, Muhammad Arshman


Hello - Ricardo here from Buenos Aires. "CLERK + NEON INTEGRATION" - you need Orlivo One to show the right apps for each school. Right now, a staff member signs in, but access depends on several connected layers. The risk is mismatched school memberships or permissions that fail silently. So I'd trace Clerk sessions into Core, then verify Neon migrations and runtime permissions. That way, each staff member sees only licensed apps for their active school. I'd also test expired sessions, multiple schools and Core outages before recommending changes. Would it help if I mapped the access flow with a test case for each failure scenario? Bottom line: you get verified findings and clear acceptance criteria before implementation. If you'd like, message me here and I'll review the repositories and authentication flow. Ricardo - Precision in every step. Value in every result.


Clerk handles auth, Neon is your Postgres backend. I would wire up Clerk webhooks to sync user records into Neon, set up migrations, and connect the repo to GitHub for clean deploys. Can start today and have the integration live in 3 days. Budget and timeline here are initial numbers based on the post, we will firm them up once I see the current repo and schema. Want me to send a quick scope doc?


SUPER MATCH "SECURE CLERK-TO-CORE INTEGRATION" — Orlivo One must show each staff member only the applications authorised for their active school, role and licence, with access enforced by the backend. I would start with the paid technical review, tracing Clerk authentication through Core's membership and permission checks, then examining Neon migrations, runtime database permissions, session validation and failure handling. The report would separate verified behaviour from assumptions, identify integration blockers, and propose the next milestone with fixed scope and acceptance criteria. If approved, I would implement changes in a separate Git branch, add tests for multi-school users, unauthorised app access and Core outages, then submit a reviewable pull request with test results and rollback instructions. Do you have a preferred local development workflow for running Orlivo One and Core together? Looking forward to working with you.


Hello tobiask17, I’m eager to support Orlivo’s integration of Clerk authentication with Neon PostgreSQL to ensure seamless, secure user access across your education platform. With extensive experience in full-stack development, API integration, and database management, I focus on delivering robust solutions that protect data integrity and streamline user roles and permissions. For Milestone 1, I will thoroughly analyze your GitHub repositories, authentication flows, and Neon database setup, identifying any blockers and validating session management, multi-school user handling, and fail-safe access restrictions. My detailed technical report will outline clear recommendations and a fixed-price plan for implementation. This approach ensures Orlivo staff only see apps they’re authorized for, while preventing unauthorized data access or system failures under Core downtime—critical for trust and compliance in EdTech. Let’s connect to discuss next steps and secure this foundational integration with precision and reliability. I’m confident my skills will deliver the secure, scalable solution Orlivo needs for long-term success. Best regards, Mayank


Hi - I am Anas from Phoenix, AZ. This looks like a straightforward but important integration piece for Orlivo: get Clerk handling auth cleanly, connect Neon PostgreSQL correctly, and make sure the GitHub workflow is set up so the project stays maintainable. The main risk here is usually wiring auth and database access in a way that works locally, then breaks in production because of env vars, callbacks, or schema assumptions. I’d approach it by first verifying the app structure, then setting up Clerk auth flows, Neon connection handling, and the GitHub repo/config so the deployment path is clean. If this is an EdTech platform, I’d also keep role-based access in mind early, since student/admin separation often needs to be enforced both in the UI and at the database/API level. I can also add a short technical handoff so the setup is documented and easy to continue. Realistically, that saves time later when you expand the platform. 1. Is this a fresh integration into an existing codebase, or should I set up the project structure from scratch? 2. Do you want simple authentication only, or should I include role-based access and database schema wiring as well? Looking forward to hearing from you.


The part I'd watch most closely is where the "active school" lives. If Clerk Organizations and Core's membership tables both track it, they can drift: a staff member in two schools might see apps licensed to the wrong one, or pass a direct link on a stale token claim. As I read it, you want Core as the single authority on access in Orlivo One, failing closed rather than trusting the token. I'd start by tracing one synthetic multi-school user end to end: Clerk JWT verification in Core (JWKS, expiry, clock skew), where the active school is chosen, and what Orlivo One does when Core times out. In parallel I'd check which Neon role the app uses at runtime, since migrations often run as owner and hide permission gaps. I've integrated Clerk with custom backends and handled PostgreSQL migrations and roles. All schema changes would stay reviewable SQL before applying. Does Core currently use Clerk Organizations at all, or only Clerk user IDs mapped to its own tables? Lautaro


I’ve built SaaS platform backends with React, Node.js and PostgreSQL, including role-based access and scalable application architecture. For this project, the key is tracing the identity-to-entitlement path before changing code, because school isolation and licence checks must be enforced consistently at Core. I’ll review the repositories, setup notes, migrations, runtime database permissions, and the current session-validation path. I’ll document verified behaviour, integration blockers, and a practical next-milestone scope with acceptance criteria. For implementation, I’ll work in a separate branch, submit a pull request, and verify active-school access, direct-link denial, and safe handling when Core is unavailable. I’ll provide concise local-run, verification, and rollback handover notes. Thanks, Kittipong


Hello. It’s clear that integrating Clerk authentication with your existing applications poses a significant challenge, especially in ensuring seamless access control and user validation. A critical insight here is the need for a thorough understanding of the current authentication flow and how it interacts with user roles and permissions. I have previously worked on a similar project where I integrated third-party authentication systems with custom backends, ensuring robust user management and security protocols. To enhance the integration process, I would focus on verifying how the current backend handles session expirations and access restrictions. This could prevent potential security vulnerabilities and improve user experience. Could you share more about any specific challenges you've faced with the current implementation? Understanding these nuances will help tailor the solution effectively. Thanks, Artiom.


Hello, You've got multiple GitHub repos for Orlivo's apps, and the first job is to untangle how Clerk auth ties into your Core backend, specifically how sessions, school memberships, and permissions flow through. The tricky part here is verifying how gracefully it handles edge cases like multi-school users or Core being down, since those could break the user experience if not handled right. I'd start by cloning the repos, running the setup, and mapping out the current auth flow end-to-end. Then I'd test the failure scenarios (expired tokens, Core downtime) to see where it cracks. The report would lay out what's solid, what needs tweaking, and a fixed-price plan for the actual integration work. I built a doc-analysis chatbot last month with RAG and PostgreSQL, so I'm comfortable digging into auth and data permissions. Do you have synthetic test users already set up for multi-school and edge-case testing, or should I generate those as part of the review?
内容来自 Freelancer News,版权归原作者所有。
阅读原文 ↗