Need some idea for cloaker features

I've been thinking about building an L3 and L7 layer cloaker that operates before traffic reaches the backend using ebpf packages and all, primarily based on network-layer filtering—a more sophisticated approach. I was curious, though: what do people usually cloak the most? Is it WordPress sites or regular static websites?

What I'm aiming to build is a hosting-based solution. You'd simply buy the hosting (with clean root access), and it would come pre-configured with cloaking—no need to add JavaScript or modify code. You could run two separate websites (or two separate WordPress installs or whole two diff apps on the same backend) on the same domain, and redirect traffic accordingly. Since the cloaking happens before any JavaScript or backend logic is loaded, it should be more secure.

If its mainly wordpress i can also add some features like auto generate a safe WordPress site that has same DOM like the money page . Idk alot of features can be added.

bumping this thread again .

bumping

Nice idea for a service

Festinger at FestingerVault (he is a member) is giving away a free cloaking wordpress plugin

See what his does and improve it

Sincerely,

The Eye

theeyeinside said:

Nice idea for a service

Festinger at FestingerVault (he is a member) is giving away a free cloaking wordpress plugin

See what his does and improve it

Sincerely,

The Eye

Click to expand...

that's looking for more inputs tho

eBPF? My god - the days you'll spend debugging this is giving me panic here.

You're going to do this at L3/L7 level - so before any backend even loads. So how will you troubleshoot why a specific routing didn't work?

Also, I think you should be platform agnostic. Not everyone will want to use WordPress.

Your system can be a combination of regular hosting + new age pages like Netlify (that can deploy straight from GitHub or Gitlab)

So I authorize a repository, git push and it gets published rapidly.

ProBuilders said:

eBPF? My god - the days you'll spend debugging this is giving me panic here.

You're going to do this at L3/L7 level - so before any backend even loads. So how will you troubleshoot why a specific routing didn't work?

Also, I think you should be platform agnostic. Not everyone will want to use WordPress.

Your system can be a combination of regular hosting + new age pages like Netlify (that can deploy straight from GitHub or Gitlab)

So I authorize a repository, git push and it gets published rapidly.

Click to expand...

"Also, I think you should be platform agnostic. Not everyone will want to use WordPress"

yeah about this part well we just have an option to quick install wordpress, what we will be providing is just a blank hosting with root access, user can install anything they want, all traffic is already filtered outside the hosting and that filter logic can be controlled by the user itself using their dashboard. That's the whole idea
basically you can say traffic will be filtered before it hits ur backend, no leaks no traces.
can also work well for payment cloaking if installed with some custom plugins easily (which is still in a testing phase but yeah its possible)

Wow how did I miss this thread? One of the most interesting cloaking discussions I've seen in recent times.

Suggestions ( Not in market )

- CTA destination links

- Instead of A/B page, content word substitution middle layer cloak.