Does it make sense to bring a front-end website editor to Rospatent?

Question

Copyright

We put together a front-end website editor.
We plan to sell a boxed version or give a ride in the Tilda/Wix-style cloud.
We think whether to carry it to register with Rospatent?
Expanded:
0. Do they do that at all?
1. Is it good for marketing? In your experience, do customers look at it? Are they specified in tenders?
2. To what extent will it provide protection from white-labeling of our boxed version by buyers (with subsequent sale under their own logo)? Or will it give no more protection than the prohibition of this in the contract of sale?
3. If it suddenly reaches the courts before the end of the registration process with Rospatent, will it take into account the fact that we have submitted an application?
4. If carried, ask for advice from the experienced (called Newskylaw). Talk about pitfalls, etc.

Answer 1

Do not confuse patents and trademarks (trademark).
You need to register a trademark.

Answer 2

Look at this and this notes about the registration of computer programs (I think it was this registration action in Rospatent that was meant, and not a trademark or patent).
0. Yes, they do.
1. Useful, especially for the state.
2. There will be protection through design works (interfaces) - you need to attach more screenshots of the program to the application or patent them separately as prototypes (see examples in the database for prototypes No. 1004350).
3. Yes, protection is given by priority date (date of application).
4. For tips, see the links above)

Answer 3

This will be protection only for countries that will be included in the list for registration. It will not be difficult for anyone who wants to release a null version under their own label under the flag of Ecuador, and hello - your registration will not give anything in this case.
0. Yes, they do if they are going to participate in local tenders.
1. Indicate if they are configured for the Soviet consumer. Actually, if marketing is aimed specifically at this target audience, then yes, it is useful.
2. In fact, none - if someone can whitelabel, then they will also be able to bypass the registration of TM.
3. In my opinion - no. Because you are not yet registered, but only submitted such an application. What if you change your mind, or do not pay, or find someone who has ALREADY submitted an application before, which will interfere with registration? Are you going to receive a certificate of who previously applied for registration? I checked one TM for registration in this way, they only gave an answer that there were none registered (!), but they don’t give a guarantee that someone didn’t submit an application the day before yesterday.
4. Подводные камни просты - указывать наиболее точное описание. Потому что если ВДРУГ кто-то захочет оспаривать - могут просто по иному переформулировать свой продукт, перекрасить - и будет считаться уже другим продуктом. Ну право же, взять Ваш продукт, вместо лого лисички сдлать лого ежевики, название СексиФокс поменять на СофтБерри, категорию ПИМ поменять на ТУДУЛИСТ, вместо оранжевого сделать фиолетовым - и вуаля, уже совсем другой продукт. А кто будет давать _экспертную оценку_ об одинаковости кода? Никто таковую не даст. А если бы и так - делают свой гит репозиторий с датой на пару лет раньше даты выпуска, запуливают код туда под открытой лицензией - и уже потом ВЫ доказваете что это не вы взяли их открытые исходники...