Security
TX-RAMP exemption for custom software: what § 6.2 says
Section 6.2 of the program manual exempts commissioned software from certification. One exclusion decides whether a build qualifies; security stays the agency's job.
Computing America. Applications, integrations, data analysis and AI/ML engineering.
Send the description
In short
- TX-RAMP's prohibition binds the buyer, and a vendor of a covered service must still be certified. Government Code § 2063.408(e) bars a state agency from entering or renewing a cloud contract unless the vendor demonstrates compliance, and § 2054.003(13) defines state agency to include university systems and institutions of higher education.
- The exemption explicitly excludes commercial off-the-shelf platforms that an agency only configures for its purposes, and the manual does not say what happens when a commissioned build is later offered to other customers.
- The exemption removes the certification step, not the security work. The manual puts responsibility for assessing and securing the service solely with the contracting agency, and § 6.1 has the agency document its scoping determinations, so ask whether it has.
- Component infrastructure-as-a-service and platform-as-a-service used to deploy the application must still comply with the same requirements. Our advice is to deploy into the institution's existing certified tenant.
Section 6.2 of the TX-RAMP Program Manual exempts custom-developed applications from certification when the institution designed, developed and commissioned them.
The question usually arrives late. A department has a workflow nothing on the market models, money has been found, and information security is looped in with one question: what is your TX-RAMP status? A firm that builds bespoke software has to answer “none,” and the project can stall while someone investigates provisional certification for a system that doesn't exist yet. The program's own manual addresses that case.
Who the rule actually binds¶
The statute's prohibition falls on the buyer, but a vendor of a covered service still has to be certified. The program manual (opens in a new tab) points at Government Code § 2063.408. Subsection (e) says a state agency “may not enter or renew a contract with a vendor to purchase cloud computing services for the agency that are subject to the state risk and authorization management program unless the vendor demonstrates compliance with program requirements.” Subsection (f) has the agency require the vendor “to maintain program compliance and certification throughout the term of the contract.” Section 4.3 of the manual lists “Maintaining compliance with security control requirements” among the provider's responsibilities. The buyer's question is what counts as demonstrating compliance, and § 6.2 answers it for commissioned builds.
A university is inside that rule, which surprises people who read “state agency” narrowly. Government Code § 2054.003(13) (opens in a new tab) defines the term to include a university system or institution of higher education as defined by § 61.003 of the Education Code. A public university in Texas is bound, and so is a community college.
What § 6.2 says¶
Version 4.0 of the program manual took effect on February 12, 2026, and it replaced 3.1. Section 6.2 is titled “Custom Developed Applications” and opens with two sentences. Check the text against the current manual on the day you rely on it.
“Cloud services that are specifically designed, developed, and commissioned by a state agency for a customized solution are not subject to TX-RAMP certification. This does not include commercial off-the-shelf software platforms that are simply configured specifically for agency purposes.”
The test doesn't ask whose cloud account the software runs in, how big the vendor is, or how sensitive the data is. It asks whether the institution specifically designed, developed and commissioned the application for a customized solution.
The agency
Dictates and assesses the security requirements before go-live
The custom application
Designed, developed and commissioned by the institution
Within: Exempt from certification.IaaS and PaaS it deploys on
Must comply; certification not required
Within: Held to the same requirements.
Section 6.2 exempts only the custom application from certification; the agency still dictates its security requirements and must ensure the platform under it complies.
SourceTX-RAMP Program Manual 4.0, §§ 6 and 6.2, as summarized in this article.
The one exclusion that decides it¶
Configuring a product is not commissioning a build¶
The manual excludes only commercial off-the-shelf platforms that are “simply configured” for agency purposes. It does not say what happens when a commissioned build is later offered to other customers. If you plan to reuse the code for other institutions, ask the security office whether it would treat the result as a product.
What stays the agency's responsibility¶
The institution decides, and documents¶
Section 5 of the manual says a state agency is ultimately responsible for determining whether a product meets the statutory definition of a cloud computing service. Section 6.1, on the neighboring exemption, adds that the agency documents its scoping determination and keeps an internal record. Section 6.2 doesn't repeat that sentence, so ask whether the institution does the same here. A vendor can supply the citation and a description of what was built.
The infrastructure underneath is the agency's to check¶
The manual makes the agency responsible for ensuring that component cloud services used to deploy the custom application (infrastructure-as-a-service, platform-as-a-service) comply with the same requirements. The manual asks that those components comply, not that they be TX-RAMP certified. Our advice is to deploy into infrastructure the institution already holds certified, usually its own tenant, and settle whose accounts those are before go-live.
Exempt from certification, not from security¶
Section 6 opens with a rule for exempt services. They must still meet the required control baselines and “all agency-specific security requirements.” Section 6.2 makes the contracting agency responsible for dictating the unique specifications and security requirements to be met before the system becomes operational. It places responsibility for assessing and securing the service solely with that agency. Expect the institution's security office to be involved during the build and to hand you its controls.
Sources
- 1.TX-RAMP Program Manual 4.0 (opens in a new tab), Texas Department of Information Resources,
- 2.Government Code § 2054.003: Definitions (opens in a new tab), Texas Legislature
Next step
Send us the project description.
The scope, request or email describing the custom system your institution wants built. We will read it against § 6.2 and say whether it raises the off-the-shelf exclusion, and what a scoped build would need to settle with your security office.
- Phone
- (214) 723-2510
- Reply
- A person replies, not a sequence: within one business day, from someone who would be on the engagement.
Packages
Start with a package
Four packages, each with its price on the page. Pick one and buy it online.
$199/month
Billed monthly
$182.42/month
Billed yearly
$499/month
Billed monthly
$457.42/month
Billed yearly
- Scammers stopped from sending email as you
- Your website and systems scanned every week
- Your email settings checked every week
- Everything in the 1 to 10 plan
- Covers up to 50 people
$199/month
after a one-time setup fee
- A site planned, designed and built for you
- Hosting and updates every month
$499/month
Billed monthly
$457.42/month
Billed yearly
$999/month
Billed monthly
$915.75/month
Billed yearly
- Your Google profile, fully set up
- A Google post every week
- 2 social posts a week
- Everything in Get found
- 4 social posts a week
- Your top 10 Google searches tracked
from$500/month
after a one-time setup fee
- Your data gathered from the tools you use
- A first analysis that answers your questions
- New findings every month
Related reading
Strategy3 min readBuild vs buy software: sort each process step before you write requirements
Sort every process step as commodity, differentiating or contextual before anyone writes a requirements document.
Delivery4 min readStatement of work template for software projects: what a SOW must include
A checklist to run before you sign, ending in a test you can give to someone who has never heard of the project.
