Your FYP shouldn't live on your laptop.
You spent months building it. You demoed it once, in a room, on your own machine. Then it stopped. An FYP Lab is where we sit down with your project, work out the right way to deploy it, and get it online where a supervisor, an employer or an actual user can open it.
From localhost to a link you can send.
We get it deployed, with you in the driving seat.
You do the work, with someone beside you who has deployed this kind of thing before. You leave knowing how to do it again.
We look at what you built
The stack, the database, the files, the bits held together with tape. No judgement. Every project has them.
We pick the right path
Shared hosting, a VPS, a static build. What your project actually needs, not the most complicated option.
You deploy it
Hosting, domain, database, environment variables, SSL. You drive, we point, and you understand every step.
We fix what breaks
Things break on first deploy. Paths, ports, connection strings, CORS. This is the part that takes the longest and it is why we do it in a room.
We test it properly
On someone else's phone, on someone else's network. Not just on the machine it was built on.
It goes live
A real URL, working, that you can put in your report, your CV and your LinkedIn.
Bring it in whatever state it is in
Half-finished is fine. Broken is fine. A project that has never left your laptop is exactly what these sessions are for. The only thing that does not work is not bringing it.
Wherever it is, there's a route.
Ready to deploy
It runs, it is mostly finished, and it needs hosting and a domain. Usually live within a single session.
Almost ready
It runs but something is hardcoded, missing or broken for anywhere but your machine. We sort it out together.
Needs development support
It is not finished yet. We tell you honestly what is left, what to prioritise, and when to come back.
A certificate
For everyone who takes part, and something concrete to attach to your project report.
Something to show
A live URL is worth more in an interview than a screenshot of a demo that no longer runs.
The community afterwards
Other teams solving the same problems, and people to ask when something breaks in two months.
This is for you if…
- You are working on a final-year project, a semester project or a university project of any size.
- It exists in some form: code, a WordPress site, a notebook, something. We cannot deploy an idea.
- You are willing to sit with it for a couple of hours rather than hand it over for someone else to do.
- Your whole team can come, or at least whoever knows how the project runs.
Not required: a finished project, a polished report, a supervisor's approval, or any prior experience with hosting.
How it works
Submit your project
The form below. Be honest about what state it is in; it changes which session we put you in.
We assess it
We read every submission and tell you which of the three routes your project is on.
Come to the lab
Bring the team, the laptop it runs on, and anything it depends on. We handle the rest.
Leave with a URL
Your project, live, plus notes on how to keep it running after the session.
Register for an FYP Lab
About five minutes. Tell us who you are — if your project is already chosen, tell us about that too, and if it isn't, come anyway.
Good to know
Does it cost anything?
No. FYP Labs are free, including the help. Hosting and a domain for your project are discussed in the session, and there is a free route for every project type.
What if my project isn't finished?
Bring it anyway. A large part of what we do is telling teams honestly what is left and what to prioritise. Plenty of projects come to one lab unfinished and a later one to deploy.
What technologies do you support?
Anything that runs on the web: PHP and WordPress, Node, React and Next, Python with Django or Flask, Laravel, static sites, and most databases. If it runs on your laptop there is usually a route to getting it online.
Can my whole team come?
Yes, and we would prefer it. Submit once as a team and bring whoever actually knows how the project runs.
Our department wants to run one for a whole cohort.
That is the best version of this. Departments and FYP coordinators can host a session for all their final-year teams at once. Get in touch through the community page.
Will it still be online after the session?
Yes, as long as the hosting stays active. We also give you notes on how to redeploy it yourself when you change something.
From localhost to a link you can send.
Bring the project. Whatever state it is in.