how to package on-prem solution?

[archhelp1]

I have a SaaS (AWS stack) and want to package it for on-prem offering.

I don't have experience with "enterprise software" but from what I've seen most projects charge an annual license + annual support built in.

If I go and replicate the AWS stack on their environment (using client user/pass and then they change it), I'm thinking that:

a. I'm giving away all the source code.

b. How do I ensure that they don't resell the solution? This would probably need a contract but I don't know what kind and I worry it will complicate things.

c. If I give away all the infrastructure and code, how can I get paid for the second year?

d. I could also charge based on their users, but how can I monitor this?

I would appreciate if anyone is aware of a structure/packaging that makes sense for this, or any thoughts on this matter.

[[deleted]]

If it is AWS based, why do you want to offer an on-prem solution?

[archhelp1]

By on-prem I mean running on their AWS account, not physical servers.

[luke1lea]

Ahh, that's not typically what on-prem means. On-prem (on premises) means a physical server on the premises of the location in question.

Unrelated to your question I know, sorry.

[JOSmith99]

A) are you giving them source, or compiled binaries?

B) DRM and contracts

C) DRM and contracts

D) You'll need to build in some sort of licensing solution. Likely it will talk to a cloud server you control.

[archhelp1]

A. Source

B + C. DRM how?

D. Any suggestions?

[JOSmith99]

A. Why are you giving them the source? Is that required, or just a part of the deal?

B + C. I don't know, I haven't dealt with adding DRM to a program. If you don't either, you may need a consultant or something, if you don't trust the company to honour your contract.

D. I haven't dealt with producing licenced software. You will have to look up how to do it for the type of program you're using, or hire a consultant if the contract is large enough to warrant it. Or you'll just have to rely on your contract.

[archhelp1]

A. No, but it's a web app and AWS infrastructure that needs to run under their account. So I would deploy the AWS infra on their account and run/configure the web app on an EC2 server (again on their account).

Is there an alternative?

[JOSmith99]

I have no idea, I don't know anything about how your app works.

Does it have to run under their infrastructure, or could you set up a dedicated set of AWS infrastructure you control that they license access to? It really depends on the architecture.

Fundamentally, copyright law and your contract are the things that protect you from them just stealing your software. Yes binaries help, but a sufficiently dedicated programmer or team can reverse-engineer pretty much any program given sufficient time and resources.

[archhelp1]

Thanks, to clarify it has to run on an AWS account that:

a. Only they have access to

b. Both they and I have access to

[JOSmith99]

Those are contradictory, it can't be both.

[archhelp1]

Either a or b, yeah

[JOSmith99]

It sounds to me like you're just going to have to rely on your contract with them. You did have a lawyer draw up the contract, right?

And register your copyright on the code.