glampware.
PLEN
Two worlds. One place.

Close to nature.
One step ahead.

Private hot tubs and a peaceful stay in the Bieszczady Mountains. Cloud architecture and DevOps for businesses, micro-enterprises and individuals. Two sides of Glampware — choose what you need.

Explore our glamping Explore IT services
A stay in the Bieszczady Mountains01 / NATURE

Slow down.
Welcome to the Bieszczady Mountains.

Glamping Bieszczady in Uherce Mineralne, Poland. Two geodesic domes, each with a private hot tub, a terrace and the comfort you need to truly unwind.

Your own space, your own paceEach dome has a private bathroom and an equipped kitchenette. Enjoy morning coffee on your terrace, a barbecue in the gazebo and an evening in your private hot tub. Heating and air conditioning keep your stay comfortable throughout the year.

Explore the Bieszczady MountainsDiscover Solina, Myczkowce and Lesko, try the rail bikes or enjoy a trip down the San River. Come for a couple’s escape or a family holiday, with a peaceful place to return to after an active day.

  • Private hot tub
  • Close to nature
  • Year-round comfort
Explore and book your stay
booking@glamping.plusBogumiła Gruca+48 693 628 647
IT contracting for businesses, micro-enterprises and individuals02 / IT

Architecture. DevOps.
Your technology partner.

We help businesses, micro-enterprises, individuals and engineering teams design architectures, migrate systems and develop their infrastructure. We join your project as a technical partner through an ongoing partnership, a defined implementation or consulting.

We match solutions to the actual scale of your project, from a first application and a clearer hosting setup to environments supporting an entire team. We start with your goal, current setup and budget to agree what needs attention now and what can wait.

You receive a clear delivery plan, changes tracked in a repository and documentation that makes future maintenance easier. Before release, we verify the solution and agree on a controlled deployment and a way to return to the previous version.

Let’s discuss your IT needs
it@glampware.plBartosz Gruca+48 665 561 021
Engineering for business

We design and build
IT infrastructure.

For businesses, micro-enterprises and individuals building their own projects, as well as product teams and software companies. We combine design with practical implementation and a documented handover to your team.

Discuss your IT project
01

Review of your current environment, selection of AWS and Oracle Cloud services, and infrastructure design. Migration plans covering dependencies, costs, cutover stages and rollback options.

02

Container platforms, AWS EKS and Linux configuration. Terraform, Ansible, Helm and GitOps for reproducible environments, controlled changes and less manual administration.

03

Design and improvement of CI/CD pipelines. Jenkins, repository integrations, artifact management and rollback procedures — from a commit to a controlled deployment.

04

Configuration, integration and migration of GitHub Enterprise, Bitbucket, Artifactory and Xray. Clear access controls, consistent workflows and tooling tailored to your team.

05

Performance troubleshooting, monitoring and log analysis. Reviews of networking, DNS, VPN and environment access. Technical documentation and a roadmap for further improvements.

06 / Security by Design

Security as a foundation.

Security is our priority and the starting point for design. We begin by understanding the risks, data and processes that need protection. We then define safeguards and build the architecture, environments and team workflows around them.

This is how we apply Security by Design: security principles inform decisions from the outset and are verified as the project develops.

  • Clear access rules

    Least privilege, identity verification and separate access to each environment. Every role has an agreed scope of responsibility.

  • Data and secrets protection

    We choose encryption, configuration storage and secrets management to match the data and risks involved in your project.

  • Controlled changes

    Versioned configuration, change reviews, isolated test environments and an agreed route to production.

  • Readiness to respond

    We plan monitoring, logs, backups and recovery scenarios. We agree how to detect problems and restore service.

Our toolkit

Technologies we work with.

We choose tools to fit your architecture, workflows and project scale. Our work covers infrastructure and platforms that support the day-to-day work of engineering teams.

  • OCIOracle Cloud Infrastructure
  • On-premPrivate infrastructure
  • AWSCloud
  • TerraformInfrastructure as Code
  • KubernetesContainer orchestration
  • AnsibleConfiguration automation
  • HelmKubernetes deployments
  • DockerContainerization
  • JenkinsCI/CD pipelines
  • GitHubEnterprise & repositories

From reproducible environments to controlled deployments — the tools serve your project’s goals.

How we work

Your goal first. The solution follows.

Every project starts with a conversation about your needs. The agreed goal, risks and acceptance criteria guide us from the initial assessment through delivery, handover and the next stage of development.

  1. We understand your goal and context

    We discuss what you want to achieve, who the solution serves and its role in your business. We agree on the expected outcome, timeline, budget and organizational constraints.

  2. We assess the environment and risks

    We review architecture, dependencies, data and resource access. Security requirements, responsibilities and areas requiring validation are identified before changes begin.

  3. We agree on the design and plan

    We compare options and explain their consequences. Together we choose tools, define scope, milestones, acceptance criteria and communication. These decisions become the delivery plan and contract.

  4. We deliver in agreed stages

    We prepare configuration, automation and test environments. We show progress, document decisions and discuss scope changes before they affect your budget or timeline.

  5. We verify and deploy

    We check functionality, permissions, monitoring and rollback scenarios within the agreed scope. Once the results are accepted, we carry out a controlled deployment with a response plan for issues.

  6. We hand over and plan ahead

    We provide documentation, configuration and operational instructions. We review the solution with your team and agree on improvements and any further support you need.

Direct contact

Let’s talk about your plans.

Choose the right contact for your stay or your technology project.

Cloud architecture and migration planning

A migration with cutover and rollback plans

A business runs its application on virtual servers. Its hosting contract is ending and the team needs a cloud migration with costs and availability under control.

How we approach it

  1. Map applications, databases and integrations. Agree availability, data location and acceptable downtime requirements.
  2. Compare AWS, Oracle Cloud, managed services and keeping some systems in place. Explain cost assumptions and trade-offs.
  3. Plan a pilot, migration waves, data synchronization, tests, cutover and rollback.

What your team receives

An architecture document, dependency map, cost assumptions and migration plan. Acceptance includes testing data recovery and key integrations before cutover.

Discuss this with Bartosz

Kubernetes and Infrastructure as Code

Environments you can reproduce

A SaaS team creates environments manually. Test and production configurations drift apart, while one person holds most of the cluster knowledge.

How we approach it

  1. Check whether Kubernetes fits the workload and the team’s operating capacity. Consider simpler alternatives.
  2. Define resources in Terraform, configuration in Ansible and applications in Helm. Agree state boundaries, permissions and secrets handling.
  3. Introduce change review, GitOps where useful, and tests for upgrades and environment recovery.

What your team receives

An infrastructure repository, setup guide and operating procedures. Acceptance includes rebuilding a test environment from code and verifying configuration and access.

Discuss this with Bartosz

DevOps and deployment automation

From manual releases to a controlled process

A software company maintains several services. Releases involve copying files and coordinating in chat. Rollback has never been rehearsed.

How we approach it

  1. Map the path from commit to production: tests, dependencies, artifacts, access and manual approvals.
  2. Build a pipeline in Jenkins or the team’s tool: tests, a versioned artifact, test deployment and production approval.
  3. Add secrets controls, release history, post-deployment checks and rollback. Agree how database migrations are handled.

What your team receives

A pipeline stored in the repository, artifact publishing rules and a release guide. Verify successful deployment, stopping on failed tests and returning to the previous version.

Discuss this with Bartosz

Developer platforms and tooling

A shared standard for code and artifacts

Repositories are spread across platforms and access rules vary between projects. Every new project starts by rebuilding the same configuration.

How we approach it

  1. Review repositories, integrations, licenses and permissions. Agree the target workflow and platform owners.
  2. Configure GitHub Enterprise or Bitbucket and Artifactory. Define artifact retention and dependency checks, for example with Xray.
  3. Pilot the migration, checking history and integrations. Document a starting standard for future projects.

What your team receives

An access matrix, migration plan, repository template and administration guide. Verify permissions and the full path from code to build and artifact publishing.

Discuss this with Bartosz

Infrastructure reliability and improvement

Less guesswork during incidents

An application slows down at peak times. The team receives plenty of alerts but cannot tell whether the cause is the database, networking or a new release.

How we approach it

  1. Agree critical user journeys and service indicators. Review metrics, logs, resource capacity and recent changes.
  2. Organize dashboards and alerts, connecting symptoms to components and owners. Check DNS, VPN and access to dependencies.
  3. Prepare response runbooks and a backup restore test. Validate performance changes under comparable load.

What your team receives

A list of causes and risks, monitoring with agreed thresholds, runbooks and an improvement plan. Evaluate results through before-and-after measurements and a recovery test.

Discuss this with Bartosz

Ongoing partnership

For infrastructure that evolves with your product, when you need technical continuity and a partner who understands earlier decisions. We add DevOps or Platform Engineering skills to your team.

How we approach it

  1. Start with an environment and access review and the most urgent risks. Agree a backlog and goals for the first stage.
  2. Work within the team’s rhythm: planning, change review, delivery and documented decisions. Balance current needs with reducing technical debt.
  3. Review progress and priorities regularly. Define involvement, availability, support and escalation terms in the contract.

Project scenario

A SaaS team prepares a major product release. First we improve deployments and monitoring, then automate environments and plan further improvements alongside application development.

What your team receives

A visible backlog, changes in repositories, up-to-date documentation and knowledge sharing. The team knows who owns tasks, what happens next and how to operate the solution.

An illustrative project scenario. Scope and acceptance criteria are agreed for your environment.

Discuss this with Bartosz

Defined implementation

For a specific outcome: a new environment, migration, Kubernetes platform or working pipeline. The project has an agreed scope, dependencies and acceptance point.

How we approach it

  1. Establish the starting point, goal, requirements and constraints. Define scope and dependencies on your team.
  2. Split delivery into milestones with demonstrations. Validate risky assumptions in a pilot before a wider rollout.
  3. Test against agreed criteria, prepare cutover and rollback, and hand over code, documentation and knowledge.

Project scenario

A business needs separate test and production environments in AWS. The project covers networking, permissions, Terraform, application deployment and monitoring. Acceptance requires rebuilding an environment and passing application tests.

What your team receives

A working solution, configuration repository, test results and operating instructions. Further development or support can be agreed as a follow-up engagement.

An illustrative project scenario. Scope and acceptance criteria are agreed for your environment.

Discuss this with Bartosz

Architecture and assessment

Before an investment, decide whether to migrate, what to modernize and where to start. We compare options against business needs and the team’s operating capacity.

How we approach it

  1. Gather requirements, diagrams, configuration, workload and cost data. Agree the questions the assessment should answer.
  2. Review dependencies, availability, access security and operations. Compare options with their risks, costs and operating effort.
  3. Discuss recommendations with the team. Separate urgent actions, longer-term improvements and assumptions to validate in a pilot.

Project scenario

A business considers Kubernetes instead of virtual machines. We compare service count, deployment frequency, costs and operating skills. The outcome may be a cluster pilot or a recommendation for a simpler platform.

What your team receives

A prioritized report, architecture options, a risk register and next steps. You have a basis for decisions, budgeting and implementation planning.

An illustrative project scenario. Scope and acceptance criteria are agreed for your environment.

Discuss this with Bartosz

glampware.pl

From a company website to a controlled publishing process: infrastructure defined in code, a preview for every change and explicit production approval.

  • Terraform
  • OCI Ampere
  • Oracle Linux
  • nginx
  • GitHub webhooks
  • systemd

Project goal

Glampware brings together two offers: stays at Glamping Bieszczady and engineering engagements for businesses, micro-enterprises and individuals. The site needed clear contact paths, a mobile layout and a way for its owner to review changes before publishing. It uses lightweight HTML and CSS with small JavaScript helpers, without an application server for the public content.

Infrastructure and Terraform

The environment runs on an Ampere A1 virtual machine with Oracle Linux in Oracle Cloud Infrastructure. A shared Terraform stack defines the VCN, subnet, internet gateway, routing, access rules, instance and reserved public IP assignment. A cloud-init bootstrap prepares the operating system. Modules separate networking, compute and addressing; lifecycle protections reduce the risk of accidentally replacing live resources.

Web layer

nginx serves the domain and static files over HTTPS. Certbot / Let’s Encrypt manages certificates. The website has Polish and English content, browser-language detection, a manual switch and shared contact details. Scripts install the web configuration and publishing services; Git tracks the website content.

PR previews and webhooks

Changes go through a feature branch and GitHub pull request. A PR webhook triggers the private stage refresh. Its receiver validates the HMAC-SHA256 signature and repository, then starts a systemd service. The preview identifies the exact PR and commit. It is separate from production and restricted by an IP access rule. A timer provides a recovery path if an event is missed.

Approval and deployment

The Approve button binds approval to a specific PR and commit. The receiver checks that the preview is current, merges through GitHub and publishes the accepted release. Deployment creates a new release directory, atomically switches the active version and checks the nginx response. A failed check restores the previous release. A separate timer also detects changes on main.

Operations and outcome

Systemd logs and the deployed commit identify what was published. The fixed deployment mechanism publishes site files without executing arbitrary PR scripts as an administrator. The resulting workflow covers infrastructure code, server setup, Git changes, private previews, approval and production deployment with rollback.

Open project in a new tab

glamping.plus

A hospitality website that connects a presentation of the property with a direct booking journey.

  • GoDaddy Website Builder
  • RoomAdmin
  • Booking
  • SEO
  • Mobile

How the project started

The starting point was the offer of two year-round geodesic domes in Uherce Mineralne: private hot tubs, amenities and a location near Bieszczady attractions. Content follows guests’ questions: what a stay looks like, what is included, what to do nearby and where to check dates.

Platform and infrastructure

The site uses GoDaddy Website Builder, which provides publishing and managed hosting. A custom domain brings the offer together. The structure covers property information, a gallery, nearby attractions, FAQs, booking and terms. Photos, descriptions and contact details guide visitors from discovery to an enquiry or reservation.

Booking integration

The booking page embeds a RoomAdmin form in an iframe. Guests move from the property presentation to an external booking engine. The booking provider maintains the widget, while the website builder holds the surrounding content and layout. Phone, email and WhatsApp provide additional contact channels.

Deployment and updates

Content and layout changes are published through the GoDaddy dashboard. Widget configuration and booking-system data are maintained separately. This separates seasonal content and photo updates from reservation management.

SEO and outcome

Content describes the location, amenities and nearby attractions; images include alternative descriptions. Navigation makes the main information and contact paths easy to find. The result is an owned presentation and direct booking channel alongside the property’s presence on accommodation portals.

Open project in a new tab

sirius.international

An interactive mapping platform with a 3D globe, external data integrations and applications for iOS and Android.

  • MapLibre GL JS
  • Python API
  • OCI
  • Terraform
  • Capacitor
  • iOS
  • Android

From idea to platform

Sirius was created to explore distributed information sources in a geographic context. Its globe and map layers bring together aviation, satellites, cameras, weather and natural events. The project develops a shared map interface, data catalogues and API integrations rather than a separate view for each provider.

Application architecture

The frontend uses MapLibre GL JS and WebGL for the map and globe. JavaScript modules handle layers, filters, dialogs and source selection. HLS playback and satellite calculation libraries support available video streams and orbital views. Some catalogues are static files; an API layer supplies changing data.

Backend and data

A Python API aggregates selected sources, caches responses and keeps provider configuration outside browser code. nginx serves the frontend and proxies requests to the API process managed by systemd. Each layer depends on its provider’s availability and freshness; the application distinguishes current data, saved datasets and retrieval failures.

OCI and Terraform

The backend runs on Oracle Linux on OCI Ampere. A shared Terraform stack defines networking, routing, access rules, compute and the public IP. A web module prepares nginx templates and a domain/HTTPS installer. Application deployment is a separate step, giving infrastructure and product releases distinct change cycles.

Deployment automation

Autodeploy checks main, retrieves a specific revision and runs syntax checks. Frontend and API releases have separate directories and active-version symlinks. The API is updated when its deployment inputs change. Health checks inspect API responses and served HTML; failed deployments trigger rollback.

iOS and Android applications

Application projects were created for both iOS and Android using Capacitor. Map code and assets are packaged with the app while data and APIs remain on the server. iOS uses Xcode and the TestFlight testing workflow; Android has a Gradle project and its own build process. Backend changes are independent of new app releases. Platform-dependent native integrations include location, sharing, saved places and notifications.

Operations and ongoing development

A prepared monitoring module checks system resources, services, HTTPS and application responses, with APNs alerts after recipient configuration. The project combines product development, data integration, Infrastructure as Code, automated deployment and mobile distribution. External libraries retain their licenses and required source attribution.

Open project in a new tab

Velocity Reborn 2 · Roblox

A Roblox racing game project, from track and gameplay design to modular race, garage and progression systems.

  • Roblox Studio
  • Luau
  • Client / Server
  • Git
  • Tests

Concept and gameplay

Velocity Reborn 2 is a racing prototype set in a coastal environment. It includes a car, a curved track with directional checkpoints, camera controls, a garage and a pre-race interface. Iterations combine scene authoring with driving tests in Roblox Studio.

Technical architecture

Luau logic is divided into client and server modules. The server manages race state, checkpoint order and rewards. Economy and profile modules handle currency, owned vehicles, upgrades and Rebirth progression. Interface and vehicle controls form a separate layer.

Code, scene and synchronization

Git stores source code and tooling; the native Roblox Studio file holds the scene, models, terrain and settings. A synchronization tool updates specified scripts in the linked project. The map is authored in the editor rather than rebuilt by gameplay code at session startup.

Testing and backups

Logic tests cover races, gates, economy and profiles; project documentation records 38 engine-independent tests. Keyboard-driven races were tested separately in Studio. Backup tooling saves code, the native scene and assets with a SHA-256 inventory. Logic and file checks complement engine testing.

Project stage

The project is at the prototype stage. Next steps cover persistent storage, full device acceptance and final presentation. Public release requires further gameplay and storage testing within Roblox.

azylnadstrumykiem.pl

Azyl nad Strumykiem — a website presenting holiday accommodation.

Explore the accommodation and details of a stay on the project’s website.

Open project in a new tab

IT contracts

An engagement that fits the goal and scale of your project.

Ways to work together

For an ongoing engagement, we join your team and develop a shared backlog. For a defined project, we agree on outcomes, milestones and acceptance criteria. Consulting helps validate assumptions, compare options and plan the next steps.

Clear terms from the outset

We agree on responsibilities, availability, communication and billing. Security requirements and environment access rules are part of these arrangements.

What you receive

A clear plan, progress updates, changes recorded in repositories and solution documentation. We work with businesses, microbusinesses and individuals.

Let’s discuss your project

Cloud & DevOps

From architecture decisions to practical operations and delivery workflows.

Architecture and infrastructure

We design AWS and Oracle Cloud environments, plan migrations and improve Linux and container platforms. Tools are chosen to fit your scale, budget and operational capabilities.

Repeatable team workflows

Terraform, Ansible, Helm and CI/CD workflows help reproduce environments, review changes and publish releases in a controlled way. We define permissions and secrets management.

A working solution

Implementation includes monitoring, documentation and rollback planning. Your team knows how to maintain and develop the environment after handover.

Let’s discuss your project

Remote collaboration

Clear communication and working agreements, wherever your team is based.

An agreed working rhythm

We agree on communication tools, availability, planning and review frequency. Tasks, decisions and outcomes are recorded in a shared workspace.

Secure access

Access to repositories and environments follows the agreed scope, roles and identity checks. We establish rules for handling secrets and removing access when the project ends.

Knowledge stays with your team

Demos and reviews make progress visible. We document configuration and provide operational instructions. Any further support is agreed separately.

Let’s discuss your project