One set of hands
When something breaks, there is one answer to who touched it. That is what makes our monitoring, our backups and our updates mean something.
Service · Why managed
Go-live is where our work starts, not where it ends. From then on the server, the updates, the backups and whatever breaks at night are ours — and you sell.
One night of a shop we run
The difference
There are three ways to a professional shop. They differ less in the software than in who is left holding it after launch.
Who runs the server
An agency buildYou — or a host you hire
A rental platformThe platform
TritonCartWe do — a dedicated install for you
Updates
An agency buildOrdered and paid for, each time
A rental platformFor everyone at once, when they ship
TritonCartAnnounced first, held in your peak season
When it breaks at night
An agency buildYour problem — or the agency’s next free slot
A rental platformA support ticket
TritonCartOur alert — we fix it, then tell you
Your shop
An agency buildBuilt for you, then frozen
A rental platformA template, plus an app for each extra
TritonCartYour brand, with modules everyone gets
After launch
An agency buildHanded over
A rental platformRented
TritonCartRun by us, for as long as the shop sells
Who has access
The server, the database and root access are ours alone. You and your team work in the admin; nobody else — not a former developer, not an agency — gets onto the machine.
When something breaks, there is one answer to who touched it. That is what makes our monitoring, our backups and our updates mean something.
Products, prices, orders, customers, promotions — everything you run day to day, with your team’s own accounts.
Every install runs on our infrastructure in Germany, more regions on request — never on a server someone else can also change.
The routine
The database backed up, encrypted, to a second region — and restored as a test, not in theory.
Uptime, certificates and failed runs watched. The alert comes to us, not to you.
Feeds imported, photos turned into web images, the catalogue kept in step with your sources.
A report of what ran, and one invoice.
Updates
A platform update is announced before it reaches your shop — what changes, and when. In your peak season, ask and we hold it.
Every shop runs a tested release from the same line — no special version for anyone, and every update reaches every shop.
Before a release moves to your shop, it is tried there first; anything that looks different, a person checks before it goes live.
Security patches go in as soon as they are out, and we tell you afterwards — announcing one would announce the hole.
When something goes wrong
Not to you, and not to your customers first. We fix it — then we tell you what happened, and what we changed so it does not happen again.
Questions
Only us. You and your team work in the admin; the server, the database and root access stay with TritonCart — so there is always one answer to who changed what.
No. Updates, monitoring and backups are only as good as our control of the machine — on a server someone else can also change, none of them would mean much. Your shop runs on our infrastructure in Germany; another region we agree before we build.
Yes. Platform updates are announced before they reach your shop, so you can ask us to hold one. Security patches are the exception: they go in straight away, and we tell you afterwards.
The alert comes to us, not to you. We fix it, then we tell you what happened and what we changed so it does not happen again.
We don’t plan to — but if we ever stop running shops, you get your whole install: the platform layer and every module it runs, so your shop keeps selling without us. Your data is yours either way: a full export at any time, in the format you need, on an open-source core (Medusa, MIT-licensed).
Ask the people who do it. We answer every e-mail ourselves, by the next business day.