Integrate Clerk and Neon for Orlivo
Budget / SalaryHourly project
TypeFreelance project
LocationRemote
Posted48 minutes ago
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 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
Apply on Freelancer →
Project sourced from Freelancer.com. Applications happen directly on the original platform — we never collect your data.