Sitejet to Plesk auto publishing with Teams or Agency plans

Hi community,

I’ve been a Sitejet user for a few months now. I was previously using Wordpress, but Sitejet’s features seem to suit my needs better. I’m currently using it via Plesk, and so far, no problems.

So I’m getting more and more interested in the “Agency” offer, only I’m afraid I don’t have a way of automatically publishing changes to a site on my Plesk-managed server. This would be very inconvenient for me, as most of my customers need special hosting conditions, and those offered directly with the package would not be suitable. Furthermore, I don’t want to export sites manually, which would mean losing forms and other functions.

Does anyone have a solution for transparently publishing a site to Plesk using a subscription package?

Thank you,
Adrien

1 Like

Hi @Adrien,

You’re absolutely right that Sitejet doesn’t currently offer built-in support for automatically publishing changes to an external server like one managed via Plesk — but there are a couple of reliable workarounds you could consider:

Option 1: Use FTP Publishing (if available in your Sitejet plan)

If your Sitejet subscription includes FTP publishing, you can:

  • Set up your Plesk-managed site’s FTP or SFTP credentials
  • Connect them in Sitejet under project settings
  • Publish directly from Sitejet to your server

This allows you to preserve forms and dynamic features without needing to export manually.

Option 2: Use Plesk’s Git Integration

You could:

  • Export your Sitejet site to a Git repository (e.g., GitHub or GitLab)
  • Set up Plesk’s Git deployment feature to auto-deploy changes from that repo

This won’t be fully “one-click” from Sitejet, but it enables a version-controlled and semi-automated workflow.

Important Note on Forms

If you export a site instead of publishing via FTP, you’ll likely lose some Sitejet-native functionality like forms or CMS features. If you’re going that route, consider:

  • Using an external form handler (e.g., Formspree, Basin, or self-hosted PHP forms)
  • Or embedding third-party form solutions

Best of luck! :rocket:

1 Like

Hey Adrien,

I think there is a mixup here. When you talk about the Agency feature, do you mean the one that is mentioned as a plan in Sitejet?

1 Like

Hi @Kalisperakichris,

I didn’t know that Sitejet offered native FTP export, which would be easy to use and also retains all the functions. If this is indeed the case for the “Agency” plan, this system would suit me perfectly! I’m going to find out which plan includes FTP export, as I can’t find anything on the Sitejet website.

Thank you very much for your help.

Adrien

1 Like

Hi @Andre,

Indeed, I refer to “Agency” as a plan in Sitejet (mentionned here : Sitejet Pricing Information | Upgrade to a Premium Plan). Does this compromise the options proposed by @Kalisperakichris?

Thank you for your help.

Adrien

H i@ Adrien,

Thanks for bringing this up—it’s a great question. I personally use Sitejet through my hosting provider, and one of the main reasons I chose it is because I retain full control over my data. Everything stays on the server, and I can export or move sites whenever needed. This was a big deciding factor for me, especially coming from WordPress.org, where data ownership was always part of the appeal.

If Sitejet’s Agency plan includes native FTP export (which it seems it might), that’s a huge advantage. It allows for full project portability—ideal for professionals and agencies who want flexibility and long-term independence from any one vendor.

That level of access is rare nowadays. Many modern platforms like Webflow or Framer offer incredible UI and features, but they often work within closed ecosystems. You’re tied to their hosting and monthly plans, and exporting a project (if possible at all) is very limited. While that model makes sense from a business perspective, it can be restricting for users who value autonomy.

From my perspective, Sitejet strikes a good balance—offering professional tools, client collaboration features, and (hopefully) open access to your work. That could make the Agency plan a very smart investment, especially if data ownership is important to you.

Let us know what you find out about FTP export—I’m sure many would benefit from the confirmation!
I found that post of @Andre very informative as well.

Best regards

Hey Adrien,

I can give you a quick overview. So, basically, Sitejet Studio is the Website Builder + the Project Manager feature. In there, you can choose different plans from Solo to Agency. The differences between the available features are shown on the page you have linked.

Team and Agency plan let you export the website. It is however a different export as you are used to when using Sitejet with Plesk. See for more details here: https://help.sitejet.io/hc/en-us/articles/24276039479319-Export-a-website

Sitejet Studio however does not give you access to the server files.

If that is something you really need, then you should stick to Plesk :slight_smile:

Sitejet Studio offers a complete agency workflow, while Sitejet Builder is a more streamlined website builder. For me, personally, I prefer Studio as it has the Project Manager + Domain Manager as a feature to work with clients.

1 Like