B2B Software Consulting in Austin
Austin has no AWS Local Zone — Texas’s two sit in Dallas and Houston — so Austin ERP hosting starts with Microsoft Azure southcentralus. Austin’s state-agency and university buyers also cannot renew a cloud contract without TX-RAMP certification. ERPStack is remote-first and engineers for both, on PostgreSQL.
Quick Answer
In short: an Austin ERP answers to the Texas Data Privacy and Security Act, whose scope test has no revenue threshold, and to TX-RAMP Level 2 control sets if you sell to a state agency. ERPStack builds it remote-first on Microsoft Azure southcentralus with ERCOT-aware failover to AWS us-east-2, and the source code is yours.
Regional Compliance
- TDPSA (Bus. & Com. Code ch. 541)
- TX-RAMP Level 1 and Level 2
- Texas Responsible AI Governance Act (HB 149)
- EAR deemed-export rule, 15 CFR §734.13
- Texas breach notice, §521.053
Security & Compliance Architecture
For Austin founders the Texas Data Privacy and Security Act, effective 1 July 2024, has one defining feature: no revenue floor.
§541.002 is an SBA test, not a revenue test
Austin SaaS teams enter scope the quarter they outgrow SBA size standards, so consent is event-sourced rows in PostgreSQL: §541.101(b)(4) bars sensitive processing without it.Browser opt-out signals, live since 1 January 2025
§541.055(e) makes a browser setting a real opt-out, so an Austin marketing stack needs a server-side handler writing it before any pixel fires. The §541.154 cure window is 30 days.TRAIGA meets the franchise-tax ledger
From 1 January 2026 HB 149 prices an uncurable violation at $80,000–$200,000, so Austin model calls get an Immutable Audit Trail. Texas levies no income tax but charges franchise tax above $2,650,000 at 0.75%.
Engineering Blueprint
The Austin PostgreSQL primary runs in Microsoft Azure southcentralus behind a Next.js API, with AWS us-east-2 held as the recovery Region.
ERCOT-aware availability
A second Austin rack is not redundancy: under SB 6, ERCOT can direct loads above 75 MW to run backup generation or curtail. The Austin standby is a Postgres replica in AWS us-east-2, on a 15-minute recovery target rather than a measured SLA.
Deemed-export RBAC for hardware teams
For Austin semiconductor and manufacturing clients, 15 CFR §734.13(b) makes releasing technology to a foreign person inside the US an export — so citizenship is a Postgres row predicate enforced by Drizzle ORM.
CREATE POLICY ear_734_13 ON drawings USING (
ear_ccl IS NULL
OR current_setting('app.citizenship') = ANY (license_countries));Built for the TX-RAMP question
We hold no TX-RAMP certification and claim none. What we ship an Austin assessor is Level 2 evidence: SSO, RBAC, Terraform-defined VPC, GitHub Actions CI/CD, Sentry telemetry.
Evaluate Your Stack
Take our interactive audit to see if your architecture is ready for operational scale.
Start Free AuditRegional Infrastructure
Infrastructure Region
Latency Metrics
Primary Datacenter
Success Stories in Austin
Real-Time Fraud Detection Platform
Real-time fraud detection and risk scoring platform
Read Case StudyTarget Industries in Austin
Frequently Asked Questions
Yes, once it outgrows SBA size standards. Bus. & Com. Code §541.002 sets no revenue or record-count threshold — scope turns on Small Business Administration status alone. An Austin SaaS company enters TDPSA scope by headcount or receipts, not by data volume.
AWS runs no Region in Texas and no Austin Local Zone; the nearest Texas edge is us-east-1-dfw-1a in Dallas. We put the Austin ERP on Microsoft Azure southcentralus and keep AWS us-east-2 as the recovery Region — deliberately off the ERCOT grid.
Odoo Enterprise, honestly, until the process stops matching the module. Austin companies at $15M ARR need usage-based billing, revenue recognition and TDPSA consent state that Odoo models awkwardly. Rebuild when customisation passes 30% of your modules.
No — ERPStack is remote-first and holds no TX-RAMP certification; the programme certifies cloud services, not development firms. Gov’t Code §2054.0593 bars a Texas agency from renewing a non-compliant cloud contract: Level 2 since 1 January 2022, Level 1 since 1 January 2024. An Austin agency buyer therefore checks the certification on AWS or Microsoft Azure, not on us.
It rules out same-grid redundancy. The EIA describes the three U.S. interconnections as operating largely independently with limited transfers, and ERCOT is uniquely balancing authority, interconnection and RTO at once. An Austin PostgreSQL standby belongs in AWS us-east-2.
SB 6 added Utilities Code §37.0561, directing the PUC to set a 75-megawatt threshold for large-load interconnection in the ERCOT power region and requiring those loads to disclose on-site backup generation and accept direction to run it or curtail during an energy emergency alert. For an Austin data-centre operator that is a scheduling constraint the ERP has to model.
From 1 January 2026. HB 149, the Texas Responsible Artificial Intelligence Governance Act, adds Bus. & Com. Code chapters 551–554, gives a 60-day cure period and prices violations at $10,000–$12,000 curable and $80,000–$200,000 uncurable. DIR runs the chapter 553 sandbox, so an Austin build shipping an AI feature needs the disclosure and logging in place before that date.