You can run on our rails: we host the site, send the email, run the backend, and pay for the models, and you get one bill and no accounts to manage. The software is always current because we keep it current for everyone.
Or you run in your own accounts, with the keys in your hands from the start. Regulated businesses and companies with their own IT often prefer this.
The important part is the same in both cases: the instruction files, the documentation, and the code are yours. Rails are a convenience, not a lock. You can move in-house on any day and nothing has to be rewritten.
Example
What it looks like.
rails.mdplain text
A client on our rails: site on our hosting, newsletter through our sender, agents on our harness. She sees one invoice. When she asked what leaving would take, the answer was: a copy of a folder.Related
Read next.
- Extended maintenanceOptional, after day 90. Maintenance and extended builds whenever you want them. Never required. Your team already owns and runs the system.Read the definition
- portabilityYour agents are files. They move to any harness, any model, any host. Leaving is copying a folder.Read the definition
- hand-offDay 90. We hand over the keys, the instructions and the files. Your team already runs it. Nothing is held.Read the definition
