Development within affiliated business InterProWebHost · Product development & cloud architecture · In development
Developing Website Traffic Security for small businesses
We are developing a managed website-security offering to help small businesses handle malicious bots and unwanted traffic while preserving access for genuine customers. Completed work includes AWS architecture and configuration, service design, service-level agreement (SLA) review coordination and a staged roadmap.
- The challenge
- Shape partner traffic-protection technology into a manageable service for small businesses.
- Current stage
- Cloud configuration and service design completed, with a staged roadmap for validation.
- Our contribution
- Connected technical implementation with customer needs, operating responsibilities and commercial planning.
- Basis for this account
- Project development reports, completed design documents and owner-confirmed infrastructure work.
The business problem
Small-business websites receive a mix of customers, useful automated services, malicious bots and other unwanted activity. Managing that mix can create a technical and support burden for the business.
Developed within InterProWebHost’s Launch, Protect, Grow direction, the proposed service brings traffic protection into the hosting experience, with simpler administration and clear responsibility for monitoring and support.
Completed development work
InterPro IT Consultants completed the following development work:
- AWS cloud architecture and configuration to support the service.
- A service scope and system model defining how requests are handled and recorded.
- An evaluation framework and repeatable testing plan.
- Analysis of alternative service approaches, customer value and operating costs.
- A staged roadmap for integration, automation and resilience.
- Service-level agreement (SLA) review coordination to clarify proposed commitments and responsibilities.
How the service would work
Partner Gatekeeper is the reference technology for a protection layer that receives requests before they reach the website. Requests are assessed against configured rules, with actions recorded for review.
Our integration planning connected that partner-provided technology with website setup, security-rule management and customer administration. It also addressed who would support the service and how recovery would be handled.
Protection without losing genuine customers
Blocking more traffic alone does not demonstrate better protection. We developed a framework to evaluate six practical questions:
- Does the service handle prohibited activity correctly?
- Does it avoid unnecessarily restricting customers and permitted automated services?
- How much delay does it add to legitimate visits?
- How much useful traffic can it serve with the resources available?
- Does protection remain available when components fail?
- What does each protected website cost to support?
Development stage and next steps
The offering remains in development. Production integration, acceptance testing and customer security outcomes are not yet established in the available records.
The roadmap begins with testing traffic handling, then moves to automating website setup and security-rule updates, followed by testing recovery from failures.
The proposed tests compare traffic with and without the protection layer under matched conditions. Results would inform release decisions across security, customer experience and operating costs.
Explore the context
What must your service prove before release?
Bring the concept, existing technical work and intended customers. We can help define the operating model, validation priorities and decisions needed before launch.