I think this sort of comes down to what you consider as 'inside' concrete5.

You should be able to place a Laravel's public directory within your concrete5 directory, renaming it to something like /admin or whatever. Then Laravel's other directories can be placed elsewhere, perhaps at the level above the website. Then you'd edit the index.php file in the public directory to point at the correct folders.

This post covers this kind of set up:
https://medium.com/@kunalnagar/deploying-laravel-5-on-godaddy-shared...

But what you're really doing is just running the Laravel app in the same web space, there's no connection between concrete5 and Laravel.

You've said you need it as a '3rd party package' - I don't think it'll work that way. You could potentially pull in individual components from Laravel and use them within concrete5, but not an entire configured app.

Instead it might be a case of working out what needs to communicate between both systems and writing some code in each system that shares the same database tables. Or you may need to write some API style interfaces in Laravel that can be used by some features in concrete5. In other words, the two installs will need to 'talk' to each other in some way, either through shared data or through messaging.

Hi mesuva..
Thank you for reply..

My requirement as follows.. Marketing team is will be handling the concrete cms.. So the way i need to develop is mostly single page controller or js file will make ajax calls for business logic.. This ajax call should be handled by laravel and should return response back to concrete..