Security
Security & ownership
Security at SilkByteX starts with ownership: your project runs in your accounts, under your name, from day one. This page states the practices that hold on every engagement — and nothing we can’t stand behind.
Code & repository ownership
Repositories for your project are created under your name from day one. The code is yours from the first commit — if you walk away mid-project, you lose nothing but us.
Infrastructure ownership
Cloud accounts, domains and production infrastructure run in your name, not ours. When we set up and run infrastructure, backups are ones we have actually restored from — tested, not just configured.
Access management
Only the senior engineers building your project hold access to it. Because the accounts are yours, you decide who has access, and you can revoke ours at any time.
Secrets & credentials
Project credentials live in accounts you own from day one. At handover, every credential and repository is transferred to you — there is nothing of yours left with us, because it was never ours to hold.
Dependency management
On a Partner retainer, monitoring, dependency and security upkeep is part of the monthly work against the agreed project scope.
Data handling
Project data lives in systems you own — your repositories and your cloud accounts — not in SilkByteX systems. The only information we hold about an enquiry is the email it arrives in.
Project handover
Handover is part of every engagement, not an exit negotiation: the build is documented and everything is transferred. Build projects include 30 days of post-launch support for fixes against the agreed project scope: defects, regressions and issues with the agreed delivered functionality. New features, redesign work, new integrations and additional product scope are separate work; we discuss the impact and agree the price before starting.
Reporting a security concern
Found something that worries you? Email hello@silkbytex.com — we reply within one business day. If you are a client, message your engineer directly.