Built on Your Infrastructure, Secured to Your Requirements, Owned by You
Every system we build is deployed to your servers or your cloud account, built to the security requirements your team sets, and handed over with the code, data, credentials and documentation. This page says exactly what that means, and what we don't claim.
Five initial discovery calls a week, one a day.
Where Your System Runs
Your system runs on infrastructure in your name: your servers, or your account with your cloud provider. We do not host client systems on TechCentera accounts, and we do not sit between you and your data. If you decide to stop working with us, nothing has to move.
That decision is made in discovery, with your team. Some clients already have a cloud account and a security policy; we build inside both. Others have neither, and we set up the account in your name on day one, so there is never a migration later.
What Is Standard on Every Build
- Role-based access. Every user sees only what their role allows. A country partner sees their own operation; the head office sees everything. Permissions are configured by your admins, not by us, after handover.
- Encrypted connections. Traffic between users, the application and integrated systems travels over encrypted connections. Nothing is sent in the clear.
- Secrets management. API keys, database credentials and tokens are stored in a secrets manager or environment configuration, never in code, never in a document and never in a chat.
- Audit logging. Who did what, and when, is recorded, so a dispute about a package, a payment or an approval has evidence behind it.
- Monitoring and alerts. Every workflow and integration we build has monitoring. When something fails, you know within minutes.
- Guardrails on AI. Where a system includes AI, nothing acts on your customers or your money without a rule saying it can: confidence thresholds, human review on the decisions that matter, and logs you can audit.
Built to Your Requirements
We build to the security and compliance requirements your team sets, and we tell you plainly when a requirement needs a specialist. If your industry or your customers impose a standard, that standard goes into the discovery output and the design, and the build is checked against it before launch.
What we will not do is present a framework as a credential. TechCentera does not hold ISO 27001, SOC 2 or any similar certification, and nothing on this site claims otherwise. If your procurement process requires a certified vendor for a part of the work, we say so at the start and help you find one; we would rather lose that piece of scope than claim something we don't have.
Your Data
Your data stays in your systems. Enrichment data, scoring rules, prompts and models in any AI feature live in your infrastructure, and nothing leaves your systems without your say. Where we integrate with third-party services (a carrier API, a payment gateway, a messaging platform, an AI model provider) the integration runs under your accounts, so the contracts, the costs and the data-handling terms are between you and the provider.
During a project, access to your data is limited to the people working on it, for as long as they are working on it. At handover, access is reviewed with you: removed where it is no longer needed, kept only where you want us on the ongoing work, and revocable by you at any time.
Payments
We do not store card data. Payments run through established gateways: Authorize.net, Stripe, Fiserv, Plug'nPay and Scotiabank's payment gateway, with others on request, under your merchant accounts. For businesses that take payment by wire only, the system records the payment and never touches a card.
AI Disclosure
Where an AI assistant, receptionist or caller speaks to your customers, it says it is an AI. That is both the honest choice and, in some markets, the legal one. AI outreach follows consent, disclosure and anti-spam rules in your market, and we decline tactics that break them.
What You Receive at Handover
- The source code, in a repository you control
- The infrastructure, in accounts in your name, with admin access held by you
- The data, in a database you own, with export documented
- Every credential, API key and service account in your name and under your control; anything our team keeps for ongoing work is granted by you and can be revoked by you
- Documentation: how the system is set up, how it runs, how to change it, and how to leave us if you ever want to
The work continues after launch. An ERP or CRM keeps changing as long as the business does: new features, new integrations, new technology, stack updates, support. Most clients keep us on for that; 98% have, and for them we become part of the team that runs the business. They stay because the system keeps changing. Leaving us would mean keeping everything and changing nothing.
Uptime and Support
Deployed systems have run at 99% uptime. Support runs in the same two-week rhythm as the build: fixes and small changes land in the next sprint; anything urgent is handled when it happens, with the monitoring telling us first.
Questions a Security Review Usually Asks
Can our IT team review the code before launch?
Yes. The repository is yours from the start, and your reviewers can read, comment and run it at any point in the build.
Can we run a penetration test?
Yes, with your own tester or one you choose. Findings go into the sprint like any other work item, and we fix them before launch.
Who has access after handover?
Your team. Any access we keep for support is granted by you, scoped to what support needs, and can be revoked by you at any time.
Do you use our data to train anything?
No. Your data is used to run your system. Where an AI feature uses a model provider, it runs under your account and that provider's terms with you.
What if a requirement is outside your expertise?
We say so, before the work starts, and help you bring in the right specialist for that piece.
Related Links
If your security review has a question this page doesn't answer, bring it to the call. Thirty minutes, with the founder, and a straight answer.
Tell Us How Your Operation Runs.
We'll Tell You What to Build.
A free 30-minute consultation with our founder. You leave with a clear view of what to build, what to automate and what to leave alone. No pitch deck. It is the shortest way to find out whether we are the right custom software development company for your operation, and we'll say so either way.
Book a Free ConsultationFive initial discovery calls a week, one a day, 11 AM to 3 PM Eastern.