Chatting with a client, he got me thinking on one thing that maybe it wasn't discussed, or I missed it..
He wants backend and frontend on two separated vps..
api.domain.com
domain.com
I think it's a valid point, right?
Has anyone from the Team thinked about it? Or it's something I can do in order to easily work with it? Anyone experience? 
We do this a lot. Is no problem. Equal to creating a Mobile Project essentially, two Projects. May have some CORS issues but should not be too hard to remedy....
It's possible. You'll have to create two projects. This is something that's most easily handled in the beginning. Trying to break this apart after building all of it in one project will be tedious.
Yes, thinked about that, but seems that the possibility of two editors at the same time is not near 
Really frustrating have to switch every minute..
Asking this because maybe this could be a good feature:
As a workaround could you not run a VM and a second instance of Wappler? Should work in theory..
Trying to avoid all that stuff, but I guess I have no other choice..
The reason why created this topic, is that I was thinking a workaround on targets, like maybe one project and upload this thing here, and this thing there..
Anyway, thanks both
You could also, for now, combine the whole Project as one, then when done copy across the API folder to a new Project. Then search and replace across the application to update all the API endpoints to match the second Project.
Messy but will get you there! Just have to keep the DB Connection name the same in the data API side when it comes time to deploy...
Haha
A little bit, but thanks for the idea
Maybe it's time to bump a feature
Em, this is probably achievable using a little bit of git magic? I’d set 2 separate servers with coolify and automated git deploys( or manual for production) and using git_ignore hooks you could apply tailor made ignore rules for the individual branches?
I’m in a middle of the project where we’re using something similar automated deploys individually while migrating database changes via flyway, and it does the trick 