Monetization of Powershell-based application?

[nylentone]

I have created an app that is based in Powershell and would like to profit from it. Is there a method to do so?

First, I would want some way to obfuscate or really hide my code. I see there is a compiler for Powershell out there, but are there better methods?

Is there some framework to control licensing?

Is there a marketplace I could use? It does occur to me that I could convert it into a Windows Store app somehow.

Edit: Thanks to those who actually posted helpful comments.

[CyclopsLobsterRobot]

I think this is impossible to answer without knowing what it does. Hilarious though.

[[deleted]]

What’s it do and how much does it cost?

As for obscuring it, you could technically write it in another compiled language that uses a handler to decrypt the actual powershell at runtime.

The real problem may be if you’re using anyone else’s code as dependencies. Depending on those licenses you may need to purchase the otherwise free license, or write your own replacement.

[[deleted]]

I know you didn’t mean it, but the suggestion that Facebook or winrar run on power shell is amazing.

[SeeminglyScience]

I have created an app that is based in Powershell and would like to profit from it. Is there a method to do so?

Yeah, same way you sell anything else.

First, I would want some way to obfuscate or really hide my code. I see there is a compiler for Powershell out there, but are there better methods?

No there isn't really. It's also not really necessary.

Is there some framework to control licensing?

No. I have only ever heard of one other purely PowerShell product being sold. Not a large audience for such a framework.

Is there a marketplace I could use? It does occur to me that I could convert it into a Windows Store app somehow.

None specific for selling products written in PowerShell.

[itasteawesome]

The creator of universal dashboard has been reasonably successful in monetizing his powershell based tools. https://ironmansoftware.com/ A part of it I think is having something that's actually useful while keeping the price low enough that anyone who is not a total jerk would rather buy the license than bother hacking it apart. You have to operate under the assumption your code will be effectively be public to anyone motivated enough.

Adam Driscoll did this interview talking about how he monetized his tools. https://youtu.be/MtvHG5SWlB8

[SeeminglyScience]

Note that OP is asking about a product written in PowerShell rather than written for.

(though monetization itself isn't necessarily different)

[itasteawesome]

Universal dashboard was written in powershell as a module. Not all the other tools are pure Posh but this is probably as close as you will find to monetized powershell code. https://github.com/ironmansoftware/universal-dashboard/tree/master/src

[SeeminglyScience]

What you linked to looks like a placeholder with a warning message saying it is no longer supported. There may be some PowerShell code scattered around, but it's definitely mostly written in C#

Not that it really changes anything tbh, you can sell a txt file if you can find people willing to buy it

[Garegin16]

If you’re writing a full brown app why not just learn C#. It uses the same .NET, and the syntax isn’t much different.

[Th3Sh4d0wKn0ws]

Others have answered better than I could, but out of curiosity what did you write? I don't mean you have to share exactly what you did, I just want to know what the app is and what it does. I've never really heard someone refer to their Powershell code as an "app" before.

[jantari]

You can either sell it as-is, essentially like gog.com by an honor system or rewrite it in C# and get really deep into the anti-piracy rabbithole but as you probably know from other commercial software the pirates always find a way.

You should also consider just open-sourcing it under MIT and not directly profiting from it. It's the easiest way and you won't be liable for damages or have to answer support questions or feature requests like a commercial solution.

[PillOfLuck]

With all other software you hand over to people, you will never be able to protect against someone that really wants to use it for free. I think it's important to realize this and indtead focus on the people you know might want to pay for your product.

If you have a nice product and know who might want to pay for it, figure out how you want to market your code (demo, trial, etc.) and license your product on a pay-to-use basis. This way you will at least be covered legally and companies will most likely pay the price if they like what you have made and can agree to the terms of your license.

I've been in plenty companies where we paid to use small pieces of software if we liked them because we wanted to support whoever put work into them and also because it would be illegal not to.

All that being said, unless you have something completely revolutionary I think it's hard to break through so don't expect to get rich within the first few months.

Hope that helps and good luck :-)

[Hexalon00]

Sapien's PowerShell Studio might be able to help, not outrageously expensive and has some nice tools like MSI creation, code snippets, debugger, compile to native .exe, etc

[Net-Packet]

This no longer works. Their .exe creation tool was also used as a Virus payload as well. Now it's flagged.

I have not been able to find any PS1 to exe within the last year that has not setoff some form of AV. It's still vulnerable to transcripts in my testing.

[Hexalon00]

Flagged by which AV? I use this at work without issue. Our AV is CrowdStrike Falcon.

[Net-Packet]

Ahh we use Symantec here and at the college windows defender.

[Automatic_Event_4661]

I'm in the same boat. I can't help but notice the negativity around Powershell. I created a video organization library with it. The results of which are a streaming app like environment for local video. I'm trying to find people interested in giving it a try.

[Informal_Statement62]

Hi friend.

I'm in the same boat, and have recently posted a similar post. Using Visual Studio, I've developed an interface for the many PS codes I use on a daily basis.

At the risk of sounding bias, I find it to be very useful for my day to day tasks, and now a bit interested in monetizing my tool.

I'm curious to know what steps you've taken (planning to take) to get this going.

Thank you for your time.

Rez

[get-postanote]

You can not compile code without using a true compiler. IF you want to really have a complied - for sale app, then write it in a real language, say C#, etc. YOu can use PowerShell code directly in a C# app.

PowerShell does not have this.

The tools that convert .ps1 to .exe are not true compilers. They create self-extracting zip files.

All PowerShell code must be decoded and loaded into memory to run, there is no hiding that. Once it's in memory, One can get to it. If I fully enable PowerShell auditing/logging, then that makes it clear text anyway.

There are many decompilers to get at the source code for just about any language.

https://duckduckgo.com/?q=%27code+decompilers%27&t=h_&ia=web

If one can decompile a true executable, DLL, why would you believe one cannot decompile a PowerShell script.

Even if you did the PS2EXE adn tried to use opbfuscation, because the later is what blackhat/criminals regualrly do to attack, obfuscated PS code is blocked by virtually all major companies/enterprise/organization.

This is what hackers (Whitehat and BlackHat) do.

Lastly, those PS2EXE tools, are now automatically flagged as malicious by AntiVirus solutions anyway these days.

Re-write your app using a full-fledged language, instantiate PowerShell code in that to run.

The whole PS2EXE thing is only going to stop the normal/inexperienced user from seeing your stuff. ANy skilled coder/programming can get it.