BearPunks on Base Meet the BearPunks: Sweet pixel art bears coming to you as PFP art collection. For sure, you will love them, they are CC0 and inspired by Larva Labs CryptoPunks. BearPunks will join the CryptoTeddies ecosystem, both created by numo (@numo_0).

BearPunks - Collection | OpenSea

OpenSea is the world&#x27;s first and largest web3 marketplace for NFTs and crypto collectibles. Browse, create, buy, sell, and auction NFTs using OpenSea today.

BANGERS - Collection | OpenSea

When the fate of Base is at stake, the only chance of survival are the Based Apes. A collection of 5,000 Futuristic Apes on Base, aiming to push the boundaries of Base for the better!

Based Apes - Collection | OpenSea

Co-Museum Founder's Pass - Collection | OpenSea

10,000 Based Cats on the Base Blockchain. Generative Pixel Art Purr-fection by Mandarinemarie

Based Cats - Collection | OpenSea

Skip to main content · Mfer Puppets · more_horiz · Items · 3,695 · Created · Apr 2024

Mfer Puppets - Collection | OpenSea

2446 boundless Ape invade the BASE world ⚔️ They&#x27;re armed, irritable, and dangerous!⚠️

Boundless Ape - Collection | OpenSea

Panachik is a 10,000 NFT collection meticulously crafted for the Base blockchain by the designer McP. McP is a well-established figure in the NFT community, verified and experienced MAYC owner. Panachik collection showcases distinctive 3D style, almost 200 unique traits and 10K random combinations.

Panachik - Collection | OpenSea

based puppets - Collection | OpenSea

OpenSeed

openseed

After a 3-month interval following the Pre-Series A funding, Lumoz receives another good news! On May 29th, Lumoz, the modular compute layer and ZK-RaaS platform, officially announced the completion of a new strategic funding round. Participating investors include IDG Blockchain, Blockchain Coinvestors, Gate Ventures, Summer Capital, EVG, SevenUpDAO, Sweep Ventures, among others. The specific amount of funding has not been disclosed. Prior to this, in March 2024, Lumoz raised a Pre-Series A funding round with a valuation of $120 million. Participating institutions included Hashkey Capital, OKX Venture, Kucoin Ventures, Polygon, Comma3, Waterdrip, YBB, Kernel Ventures, D11-Labs, MH Ventures, Kronos Research and Fermion Capital. The Lumoz team revealed that the new funds will be used to further expand the Lumoz team, develop the modular computing power layer, and advance the construction and technological innovation of the ZK-RaaS platform. "After the announcement of the previous funding round, many venture capitalists eagerly approached Lumoz, prompting us to initiate another strategic funding round within a short timeframe. In this round, we have once again attracted a group of exceptional investors and partners who have full confidence in Lumoz's vision, products, and team. They are enthusiastic about providing multi-faceted support, including funding, expertise, and resources, which will undoubtedly have a positive impact on Lumoz's future," Lumoz CEO & Co-founder Nanfeng said. Over the past six months, Lumoz has entered a new phase of development. The successful launch of the ETH Layer 2 network, ZKFair, and the BTC Layer 2 network, Merlin Chain, has made Lumoz's "one-click chain deployment" a focal point of market attention. Currently, Lumoz is receiving an increasing number of customer demands, and it is anticipated that dozens of ZK-Rollups will be generated through Lumoz's RaaS platform and supported by its underlying computing power in the latter half of this year. For a ZK-Rollup, the computational cost of ZKP far exceeds that of data availability (DA), even accounting for more than 50% of the total cost. Therefore, the computational gap in this area and the immense market potential are significant. In response, Lumoz has taken the lead in introducing the Modular Compute Layer, which effectively utilizes idle computing power in the market to provide modularized computing support for ZK-Rollups. In terms of implementation, Lumoz's unique ZK-PoW algorithm efficiently combines miners' computational resources with various Rollups, enabling the provision of distributed computing power for various ZK-Rollups and the generation of ZKPs. At the same time, Lumoz continues to make continuous improvements in ZKP computation and submission. Recently, Lumoz introduced support for Op Stack + ZK Fraud Proof, pioneering a new mode for L2 architecture. Following this, they launched zkProver and zkVerifier based on EigenLayer, significantly enhancing computational and verification efficiency. These advancements ensure the security and profitability of the entire process. The latest roadmap reveals that Lumoz will soon release a new AI + PoW Chain, multiple ETH Layer 2 chains, Layer 3 chains, and BTC Layer 2 chains. Additionally, Lumoz will open the decentralized node registration globally to ensure network security after the Mainnet launch. Stay tuned for more updates! After a 3-month interval following the Pre-Series A funding, Lumoz receives another good news! On May 29th, Lumoz , the modular compute layer and ZK-RaaS platform, officially announced the completion of a new strategic funding round. Participating investors include IDG Blockchain, Blockchain Coinvestors, Gate Ventures, Summer Capital, EVG, SevenUpDAO, Sweep Ventures, among others. The specific amount of funding has not been disclosed. Lumoz Lumoz Prior to this, in March 2024, Lumoz raised a Pre-Series A funding round with a valuation of $120 million. Participating institutions included Hashkey Capital, OKX Venture, Kucoin Ventures, Polygon, Comma3, Waterdrip, YBB, Kernel Ventures, D11-Labs, MH Ventures, Kronos Research and Fermion Capital. raised raised The Lumoz team revealed that the new funds will be used to further expand the Lumoz team, develop the modular computing power layer, and advance the construction and technological innovation of the ZK-RaaS platform. The Lumoz team revealed that the new funds will be used to further expand the Lumoz team, develop the modular computing power layer, and advance the construction and technological innovation of the ZK-RaaS platform. "After the announcement of the previous funding round, many venture capitalists eagerly approached Lumoz, prompting us to initiate another strategic funding round within a short timeframe. In this round, we have once again attracted a group of exceptional investors and partners who have full confidence in Lumoz's vision, products, and team. They are enthusiastic about providing multi-faceted support, including funding, expertise, and resources, which will undoubtedly have a positive impact on Lumoz's future," Lumoz CEO & Co-founder Nanfeng said. Over the past six months, Lumoz has entered a new phase of development. The successful launch of the ETH Layer 2 network, ZKFair, and the BTC Layer 2 network, Merlin Chain, has made Lumoz's "one-click chain deployment" a focal point of market attention. Currently, Lumoz is receiving an increasing number of customer demands, and it is anticipated that dozens of ZK-Rollups will be generated through Lumoz's RaaS platform and supported by its underlying computing power in the latter half of this year. For a ZK-Rollup, the computational cost of ZKP far exceeds that of data availability (DA), even accounting for more than 50% of the total cost. Therefore, the computational gap in this area and the immense market potential are significant. In response, Lumoz has taken the lead in introducing the Modular Compute Layer, which effectively utilizes idle computing power in the market to provide modularized computing support for ZK-Rollups. In terms of implementation, Lumoz's unique ZK-PoW algorithm efficiently combines miners' computational resources with various Rollups, enabling the provision of distributed computing power for various ZK-Rollups and the generation of ZKPs. At the same time, Lumoz continues to make continuous improvements in ZKP computation and submission. Recently, Lumoz introduced support for Op Stack + ZK Fraud Proof, pioneering a new mode for L2 architecture. Following this, they launched zkProver and zkVerifier based on EigenLayer, significantly enhancing computational and verification efficiency. These advancements ensure the security and profitability of the entire process. support support launched launched The latest roadmap reveals that Lumoz will soon release a new AI + PoW Chain, multiple ETH Layer 2 chains, Layer 3 chains, and BTC Layer 2 chains. Additionally, Lumoz will open the decentralized node registration globally to ensure network security after the Mainnet launch. Stay tuned for more updates!

Lumoz Successfully Concludes Strategic Round - Registration of Decentralized Nodes Will be Opened 

লুমোজ সফলভাবে কৌশলগত রাউন্ড শেষ করেছে, বিকেন্দ্রীভূত নোডগুলির নিবন্ধন খোলা হবে 

Lumoz schließt strategische Runde erfolgreich ab, Registrierung dezentraler Knoten wird eröffnet

Lumoz concluye con éxito la ronda estratégica y se abrirá el registro de nodos descentralizados 

Lumoz conclut avec succès le cycle stratégique et l'enregistrement des nœuds décentralisés sera ouvert 

लुमोज़ ने रणनीतिक दौर का सफलतापूर्वक समापन किया, विकेंद्रीकृत नोड्स का पंजीकरण खोला जाएगा

Lumozが戦略ラウンドを成功裏に終了、分散ノードの登録が開始される

Lumoz는 전략적 라운드를 성공적으로 마치고 분산형 노드 등록이 시작됩니다 

Lumoz conclui rodada estratégica com sucesso, registro de nós descentralizados será aberto 

Lumoz успешно завершает стратегический раунд, будет открыта регистрация децентрализованных нод 

Lumoz Stratejik Turu Başarıyla Tamamladı, Merkezi Olmayan Düğümlerin Kayıtları Açılacak 

Lumoz kết thúc thành công vòng chiến lược, đăng ký các nút phi tập trung sẽ được mở 

Lumoz 成功完成战略轮融资，将开放去中心化节点注册

In this session of our "Behind the Startup" series, we sit down with Zad, the visionary founder of OpenCred, to explore the revolutionary concept of tokenizing trust in the Web3 environment. As a Stanford-certified expert in blockchain and cryptography, Zad discusses the inception of OpenCred, its unique approach to digital identity through eSFT tokens, and its ambitious mission to reshape social and economic interactions online. Ishan Pandey: Hi Zad, great to have you here for our "Innovators in Web3" series. Can you tell us about your background and what led you to create OpenCred? Zad: As a postgraduate in Blockchain Strategy and Stanford-certified cryptography expert, I have spent years conducting cutting-edge research in asset tokenization, DID, and cybersecurity. Trust is actually one of the most difficult things to measure and quantify, no matter “IRL” or online. Now with blockchain and tokens we finally have the tools to tackle this problem in a novel way. I founded OpenCred to bring tokenized trust to the Web3 industry, unleash the hidden potential that lies in social relationships, and eventually enable the establishment of a decentralized society. Ishan Pandey: Could you start by explaining what OpenCred is and what specific gap in the Web3 space it aims to fill? Zad: OpenCred is a decentralized Web3 credit protocol that applies a new token standard called “eSFT” to tokenize trust relationships into tangible and quantifiable economic assets. Our vision is to empower users to monetize their online activity while guaranteeing data privacy and ownership. By providing a blockchain-based solution for establishing and measuring trust relationships, OpenCred fills a crucial gap in the Web3 ecosystem: enabling trustworthy interactions and collaboration without relying on centralized intermediaries or KYC. Ishan Pandey: In the deck, you mention that OpenCred introduces a groundbreaking trust value (credit) quantification for Web3. Can you elaborate on how this works and why it's important? Zad: OpenCred aggregates both on-chain (e.g., DeFi TVL, smart contract interactions) and off-chain data (e.g., social media followers and interactions) to tokenize trust in the form of CRED tokens. This means users can increase their personal trust value by increasing their online activity and footprint. Each CRED is unique to the user and contains a number of fungible Score Tokens (ST) that determine the value of a user’s CRED. By thus providing a measurable and objective way to assess trustworthiness, OpenCred enables secure, traceable, and efficient trust-based interactions in various Web3 applications, such as social media, e-commerce, DeFi, and gaming. This groundbreaking mechanism is crucial for fostering a trustworthy environment in the digital space and enabling countless new use cases in many areas from B2B to B2C to C2B to C2C. Ishan Pandey: The CRED token seems to be a key component of the OpenCred ecosystem. Can you explain its dual nature as a semi-fungible token and how it represents both identity and trustworthiness? And how does this design benefit users of your platform? Zad: CRED tokens are a groundbreaking innovation of OpenCred, creating a new token standard we call embedded semi-fungible token (eSFT) that combines both non-fungible (unique) and fungible (interchangeable) properties. The non-fungible part of the token represents a user's unique identity within the OpenCred protocol, ensuring that each user has a distinct and verifiable presence. On the other hand, the fungible part of the token quantifies the user's trustworthiness, which is determined by their interactions (on-chain & off-chain) and the amount of CRED tokens they receive from others. This design benefits users by empowering them to monetize their online activity and social relationships. Moreover, by tokenizing trust and making it quantifiable and tangible, we are creating a new kind of asset that simply has not existed before, thereby creating huge value. Ishan Pandey: How does sending CRED between users facilitate the building of a trustable and quantifiable social graph in Web3? Zad: When a user sends CRED tokens to another user, they are essentially establishing a trust relationship that is recorded on the blockchain. This transaction signifies that the sender trusts the recipient to a certain degree, based on their interactions, reputation, or other factors. As users continue to interact and send CRED tokens to each other, a dynamic, evolving on-chain social graph emerges. The social graph is quantifiable and traceable. This quantification of trust enables users to make informed decisions when interacting with others, as they can assess the trustworthiness of potential collaborators, partners, or service providers based on their position in the social graph. Ishan Pandey: With OpenCred positioning itself as a provider of "Trust as a Service," how do you ensure the reliability and security of the trust metrics generated by your protocol? Zad: There is a clear friction between incentivizing users on the one hand and ensuring the authenticity of trust relationships on the other hand. We are aware of this and will tackle this problem in multiple ways. First of all, we will connect the sending of CRED with some actions such as “follow”, “like”, etc., so that the transfer of CRED corresponds with the establishment of a meaningful trust relationship. Secondly, we will implement punishments for sybil attackers and other malicious behavior. Additionally, OpenCred implements a multi-layered governance model that involves community participation and decentralized decision-making. This approach helps to maintain the integrity and fairness of the trust metrics, as the community can collectively monitor and flag any suspicious activities or attempts to manipulate trust scores. To further enhance the reliability of trust metrics, OpenCred incorporates a reputation staking mechanism, where users are required to stake a portion of our governance tokens to participate in trust-building activities. OpenCred places a strong emphasis on user education and awareness. By providing clear guidelines, tutorials, and best practices for using the trust protocol. Ishan Pandey: How do you plan to drive adoption and grow the OpenCred ecosystem, particularly in terms of attracting both users and developers? Zad: OpenCred actively seeks partnerships and collaborations with established Web3 projects across various sectors, such as social media, e-commerce, gaming, and decentralized finance (DeFi). We currently have established partnerships with over 10 Web3 projects with close to 1 million daily active users ready to onboard our protocol once it is live. To attract developers, OpenCred will provide a range of tools, SDKs, and documentation to facilitate the integration of its trust protocol into various applications. The protocol will offer developer grants, hackathons, and bounty programs to incentivize the creation of innovative trust-based solutions. By fostering a vibrant developer community and providing the necessary resources and support, OpenCred aims to accelerate the development of a diverse range of dApps that leverage its trust infrastructure. OpenCred's tokenomics model is designed to incentivize user participation and ecosystem growth. The governance token serves as the primary means of interaction within the OpenCred ecosystem, used for establishing trust relationships, staking, and accessing trust-based services. The protocol will implement a reward system that incentivizes users to actively participate in trust-building activities, such as providing accurate trust assessments, staking tokens, and contributing to the network's security. These incentives will drive user adoption and encourage long-term engagement with the OpenCred ecosystem. Don’t forget to like and share the story! Vested Interest Disclosure: This author is an independent contributor publishing via our business blogging program. HackerNoon has reviewed the report for quality, but the claims herein belong to the author. #DYOR. In this session of our "Behind the Startup" series, we sit down with Zad, the visionary founder of OpenCred, to explore the revolutionary concept of tokenizing trust in the Web3 environment. As a Stanford-certified expert in blockchain and cryptography, Zad discusses the inception of OpenCred, its unique approach to digital identity through eSFT tokens, and its ambitious mission to reshape social and economic interactions online. Ishan Pandey: Hi Zad, great to have you here for our "Innovators in Web3" series. Can you tell us about your background and what led you to create OpenCred? Ishan Pandey: Zad: As a postgraduate in Blockchain Strategy and Stanford-certified cryptography expert, I have spent years conducting cutting-edge research in asset tokenization, DID, and cybersecurity. Trust is actually one of the most difficult things to measure and quantify, no matter “IRL” or online. Now with blockchain and tokens we finally have the tools to tackle this problem in a novel way. I founded OpenCred to bring tokenized trust to the Web3 industry, unleash the hidden potential that lies in social relationships, and eventually enable the establishment of a decentralized society. Zad: Ishan Pandey: Could you start by explaining what OpenCred is and what specific gap in the Web3 space it aims to fill? Ishan Pandey: Zad: OpenCred is a decentralized Web3 credit protocol that applies a new token standard called “eSFT” to tokenize trust relationships into tangible and quantifiable economic assets. Our vision is to empower users to monetize their online activity while guaranteeing data privacy and ownership. By providing a blockchain-based solution for establishing and measuring trust relationships, OpenCred fills a crucial gap in the Web3 ecosystem: enabling trustworthy interactions and collaboration without relying on centralized intermediaries or KYC. Zad: Ishan Pandey: In the deck, you mention that OpenCred introduces a groundbreaking trust value (credit) quantification for Web3. Can you elaborate on how this works and why it's important? Ishan Pandey: Zad: OpenCred aggregates both on-chain (e.g., DeFi TVL, smart contract interactions) and off-chain data (e.g., social media followers and interactions) to tokenize trust in the form of CRED tokens. This means users can increase their personal trust value by increasing their online activity and footprint. Each CRED is unique to the user and contains a number of fungible Score Tokens (ST) that determine the value of a user’s CRED. By thus providing a measurable and objective way to assess trustworthiness, OpenCred enables secure, traceable, and efficient trust-based interactions in various Web3 applications, such as social media, e-commerce, DeFi, and gaming. This groundbreaking mechanism is crucial for fostering a trustworthy environment in the digital space and enabling countless new use cases in many areas from B2B to B2C to C2B to C2C. Zad: Ishan Pandey: The CRED token seems to be a key component of the OpenCred ecosystem. Can you explain its dual nature as a semi-fungible token and how it represents both identity and trustworthiness? And how does this design benefit users of your platform? Ishan Pandey: Zad: CRED tokens are a groundbreaking innovation of OpenCred, creating a new token standard we call embedded semi-fungible token (eSFT) that combines both non-fungible (unique) and fungible (interchangeable) properties. The non-fungible part of the token represents a user's unique identity within the OpenCred protocol, ensuring that each user has a distinct and verifiable presence. On the other hand, the fungible part of the token quantifies the user's trustworthiness, which is determined by their interactions (on-chain & off-chain) and the amount of CRED tokens they receive from others. This design benefits users by empowering them to monetize their online activity and social relationships. Moreover, by tokenizing trust and making it quantifiable and tangible, we are creating a new kind of asset that simply has not existed before, thereby creating huge value. Zad: Ishan Pandey: How does sending CRED between users facilitate the building of a trustable and quantifiable social graph in Web3? Ishan Pandey: Zad: When a user sends CRED tokens to another user, they are essentially establishing a trust relationship that is recorded on the blockchain. This transaction signifies that the sender trusts the recipient to a certain degree, based on their interactions, reputation, or other factors. As users continue to interact and send CRED tokens to each other, a dynamic, evolving on-chain social graph emerges. The social graph is quantifiable and traceable. This quantification of trust enables users to make informed decisions when interacting with others, as they can assess the trustworthiness of potential collaborators, partners, or service providers based on their position in the social graph. Zad: Ishan Pandey: With OpenCred positioning itself as a provider of "Trust as a Service," how do you ensure the reliability and security of the trust metrics generated by your protocol? Ishan Pandey: Zad: There is a clear friction between incentivizing users on the one hand and ensuring the authenticity of trust relationships on the other hand. We are aware of this and will tackle this problem in multiple ways. First of all, we will connect the sending of CRED with some actions such as “follow”, “like”, etc., so that the transfer of CRED corresponds with the establishment of a meaningful trust relationship. Secondly, we will implement punishments for sybil attackers and other malicious behavior. Additionally, OpenCred implements a multi-layered governance model that involves community participation and decentralized decision-making. This approach helps to maintain the integrity and fairness of the trust metrics, as the community can collectively monitor and flag any suspicious activities or attempts to manipulate trust scores. To further enhance the reliability of trust metrics, OpenCred incorporates a reputation staking mechanism, where users are required to stake a portion of our governance tokens to participate in trust-building activities. OpenCred places a strong emphasis on user education and awareness. By providing clear guidelines, tutorials, and best practices for using the trust protocol. Zad: Ishan Pandey: How do you plan to drive adoption and grow the OpenCred ecosystem, particularly in terms of attracting both users and developers? Ishan Pandey: Zad: OpenCred actively seeks partnerships and collaborations with established Web3 projects across various sectors, such as social media, e-commerce, gaming, and decentralized finance (DeFi). We currently have established partnerships with over 10 Web3 projects with close to 1 million daily active users ready to onboard our protocol once it is live. To attract developers, OpenCred will provide a range of tools, SDKs, and documentation to facilitate the integration of its trust protocol into various applications. The protocol will offer developer grants, hackathons, and bounty programs to incentivize the creation of innovative trust-based solutions. Zad: By fostering a vibrant developer community and providing the necessary resources and support, OpenCred aims to accelerate the development of a diverse range of dApps that leverage its trust infrastructure. OpenCred's tokenomics model is designed to incentivize user participation and ecosystem growth. The governance token serves as the primary means of interaction within the OpenCred ecosystem, used for establishing trust relationships, staking, and accessing trust-based services. The protocol will implement a reward system that incentivizes users to actively participate in trust-building activities, such as providing accurate trust assessments, staking tokens, and contributing to the network's security. These incentives will drive user adoption and encourage long-term engagement with the OpenCred ecosystem. Don’t forget to like and share the story! Vested Interest Disclosure: This author is an independent contributor publishing via our business blogging program. HackerNoon has reviewed the report for quality, but the claims herein belong to the author. #DYOR. Vested Interest Disclosure: This author is an independent contributor publishing via our business blogging program . HackerNoon has reviewed the report for quality, but the claims herein belong to the author. #DYOR. Vested Interest Disclosure: business blogging program business blogging program

How OpenCred Makes Trust Tangible via Tokenization

কিভাবে ওপেনক্রেড অনলাইনে বিশ্বাস তৈরি করতে টোকেনাইজেশন ব্যবহার করে

Wie OpenCred Tokenisierung nutzt, um Online-Vertrauen aufzubauen

Cómo OpenCred utiliza la tokenización para generar confianza en línea

Comment OpenCred utilise la tokenisation pour renforcer la confiance en ligne

ओपनक्रेड ऑनलाइन विश्वास बनाने के लिए टोकनाइजेशन का उपयोग कैसे करता है

OpenCred がトークン化を利用してオンラインで信頼を築く方法

OpenCred가 토큰화를 사용하여 온라인 신뢰를 구축하는 방법

Como o OpenCred usa tokenização para construir confiança online

Как OpenCred использует токенизацию для укрепления доверия в Интернете

OpenCred Çevrimiçi Güven Oluşturmak İçin Tokenizasyonu Nasıl Kullanıyor?

Cách OpenCred sử dụng mã thông báo để xây dựng niềm tin trực tuyến

OpenCred 如何使用代币化在线建立信任

What are we talking about here? As part of my job, I advise a lot of customers who use AWS. Many of them build complex systems on top of services. AWS OpenSearch is typically included in the system landscape to cover a wide range of different business cases, some of which require an Internet-accessible cluster with HTTP basic authentication. AWS does not give this capability out of the box; thus, in this article, I will demonstrate how to leverage AWS native services to publish your OpenSearch cluster to the Internet. AWS The current limitations OpenSearch cluster can be deployed in two modes with the following features VPC based Public domain Only private endpoint in the following format https://vpc-domain-name Public endpoint in the following format https://search-domain-name Cluster health tab does not include shard information, and the Indices tab isn't present. All information about cluster health and indexes are available Security is based on AWS security groups Security is based on IP-based access policies Dashboards are available only from VPC and requires VPN or something else for being accessible Dashboards are available publicly for IP range that’s configured via IP-based access policies AWS currently does not provide any out-of-the-box way for publishing an OpenSearch cluster with basic HTTP authentication to the Internet for any IP range (e.g.: ). It is possible to configure an AWS IAM Policy to allow a certain IP range or to utilize a publicly open cluster with SAML authorization; however, this is not suitable for cases such as mobile clients or TV set-top boxes, where the client can have any unpredictable IP address and dev team does not have the capacity for SAML implementation. 0.0.0.0/0 Maybe in the future, there will be something like an RDS proxy, but so far, AWS has no public plans for this feature. Solutions The official AWS proposal based on Nginx The AWS documentation recommends using a reverse proxy based on a highly available EC2 Nginx cluster. It's a good approach, but it requires a lot of extra effort for Nginx maintenance, which would be inconvenient in the case of a large number of clusters. In addition, as AWS does not provide highly available Nginx as a service, you will be unable to configure your infrastructure using a single tool such as Terraform, Pulumi, or CloudFormation. OpenSearch The solution based on AWS native services My approach, which I recommend for use in production environments, is based on AWS Application load balancer (ALB). Nginx can be skipped because ALB provides the same functionality as Nginx for all basic scenarios and requires no additional configuration or automation work. AWS ALB points to an IP address target group that contains a set of private OpenSearch IP addresses, and the OpenSearch cluster should be configured in VPC mode. It is also important to configure HTTP redirects at the ALB level in this configuration, as seen in the image below. ALB targets should also require the configuration of health checks because without them, OpenSearch IP addresses will be removed from IP pools. Keep in mind that the http code must be added to the list of successful health check codes when you are using basic HTTP authentication. 401 Configuring the ALB target group once is insufficient. Any OpenSearch cluster change can cause the IP address to change, so to ensure that the target groups contain all OpenSearch IPs at all times, the IP addresses pool should be maintained by a simple Lambda function that runs once per hour and verifies that all OpenSearch IPs are present and actual. The complete AWS function code is provided below. import boto3
import socket

def lambda_handler(event, context):
    # Initialize AWS clients
    elasticsearch = boto3.client('es')
    elbv2 = boto3.client('elbv2')

    # Retrieve target group ARN and OpenSearch domain name from event
    target_group_arn = event.get('targetGroupARN')
    open_search_domain_name = event.get('openSearchDomainName')

    # Describe OpenSearch cluster to retrieve DNS endpoint
    response = elasticsearch.describe_elasticsearch_domain(DomainName=open_search_domain_name)
    opensearch_dns = response['DomainStatus']['Endpoints']['vpc']

    # Resolve DNS to get IP addresses
    opensearch_ips = socket.gethostbyname_ex(opensearch_dns)[2]
    print(f"OpenSearch IPs are: {opensearch_ips}")

    # Describe existing IPs in the EC2 target group
    target_group_info = elbv2.describe_target_health(TargetGroupArn=target_group_arn)
    existing_ips = [target['Target']['Id'] for target in target_group_info['TargetHealthDescriptions']]

    # Compare IPs to determine new ones and remove old ones
    ips_to_add = list(set(opensearch_ips) - set(existing_ips))
    ips_to_remove = list(set(existing_ips) - set(opensearch_ips))

    # Update the target group
    if ips_to_add:
        elbv2.register_targets(TargetGroupArn=target_group_arn, Targets=[{'Id': ip} for ip in ips_to_add])
    if ips_to_remove:
        elbv2.deregister_targets(TargetGroupArn=target_group_arn, Targets=[{'Id': ip} for ip in ips_to_remove])

    return {
        'statusCode': 200,
        'body': 'Updated EC2 target group with OpenSearch IPs.'
    } The lambda function can be deployed in VPC mode. It’s more secure but not mandatory. In the beginning, you may provide only permissions for your Lambda’s IAM role, as shown in the code snippet below. es:* {
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Principal": {
        "AWS": [
          "arn:aws:iam::123456789012:user/test-user"
        ]
      },
      "Action": [
        "es:*"
      ],
      "Resource": "arn:aws:es:us-west-1:987654321098:domain/test-domain/*"
    }
  ]
} For a variety of reasons, connecting to an OpenSearch cluster with a floating IP address is inconvenient. All modern architectures use DNS to hide a pure IP address. We'll do the same via AWS Route53. Unfortunately, the Route53 DNS record is insufficient because ALB would display problems linked to HTTP certificate mismatches. We must generate a valid TLS certificate and attach it to an ALB listener to avoid HTTPS connection issues while using DNS. can be used to issue a purchased certificate, but I prefer free Let's Encrypt certificates. AWS does not natively support Let's Encrypt and Certificate Manager integration, so I created an AWS Lambda that automatically issues and renews TLS certificates a long time ago and proposes using it in the suggested design. This Lambda's sources may be found at AWS Certificate Manager https://github.com/kvendingoldo/aws-letsencrypt-lambda. Security highlights Security is not covered in this article, but I can not highlight two critical points: Don't forget to configure your AWS security groups correctly; you only need to allow the required port (443 in our example). Use AWS Trust Advisor to ensure that all useless ports are blocked. It would be a good idea to have different users with different types of rights when using OpenSearch HTTP basic authentication. Do not use an admin user with full cluster access. It would be preferable to have multiple users, each with access to a subset of OpenSearch indexes. You can keep all password information in AWS Secret Manager for simplified password management. Summary It is possible to avoid using a High Availability Nginx cluster in your architecture. It will save you money and configuration time. Instead of using tools like Terraform or Pulumi, use the lambda function to keep your ALB's target group up to date. It is critical to check the target pool's validity on a regular basis. Don't forget about security when it comes to implementation. Take note of AWS subnets, security groups, and OpenSearch users. Use as many AWS native components as possible. All of them can be configured using IaC tools like Terraform, Pulumi, or CloudFormation. Although EC2 instances can be configured using IaC tools, the provisioning, configuration, and launch times are substantially longer than with pure AWS ALB. Useful links AWS OpenSearch access proxy AWS Let’s encrypt lambda

How to Make AWS OpenSearch Publicly Accessible Without nginx Proxy

Greetings Comrades! One of the strangest logging setups I ever had - AWS ALB controller logs. Really, look at the scheme: 1. S3 Bucket for ALB Logs I assume that you already have an ALB Controller in your EKS Cluster. So, we should create an S3 bucket and enable the SQS trigger with Terraform: ###
# ALB Controller Logs S3 Bucket
###

resource "aws_s3_bucket" "alb_logs" {
  bucket = "alb-logs"
}

resource "aws_s3_bucket_lifecycle_configuration" "alb_logs" {
  bucket = aws_s3_bucket.alb_logs.id

  rule {
    id = "log"

    expiration {
      days = 3
    }

    status = "Enabled"
  }
}

resource "aws_s3_bucket_policy" "alb_logs" {
  bucket = aws_s3_bucket.alb_logs.id
  policy = data.aws_iam_policy_document.alb_logs_bucket_policy.json
}

data "aws_iam_policy_document" "alb_logs_bucket_policy" {
  statement {
    principals {
      type        = "AWS"
      identifiers = ["arn:aws:iam::127311923021:root"] <--- it should be like this!!!
    }
    actions   = ["s3:*"]   <--- I`m so lazy
    resources = ["${aws_s3_bucket.alb_logs.arn}/*", ]
  }
} 2. S3 Trigger to SQS Queue ###
# ALB Logs SQS Queue
###

resource "aws_sqs_queue" "alb_logs" {
  name                    = "alb-logs"
  sqs_managed_sse_enabled = false
}

data "aws_iam_policy_document" "alb_logs_policy" {
  statement {
    effect = "Allow"

    principals {
      type        = "*"   <--- Wow again!!!
      identifiers = ["*"]   <--- And again!!!
    }

    actions   = ["sqs:SendMessage"]
    resources = [aws_sqs_queue.alb_logs.arn]

    condition {
      test     = "ArnEquals"
      variable = "aws:SourceArn"
      values   = [aws_s3_bucket.alb_logs.arn]
    }
  }
}

resource "aws_sqs_queue_policy" "alb_logs" {
  queue_url = aws_sqs_queue.alb_logs.id
  policy    = data.aws_iam_policy_document.alb_logs_policy.json
}

resource "aws_s3_bucket_notification" "alb_logs" {
  bucket = aws_s3_bucket.alb_logs.id

  queue {
    id        = "alb-logs"
    queue_arn = aws_sqs_queue.alb_logs.arn
    events    = ["s3:ObjectCreated:*"]
  }
} 3.  Installing and Configuring Vector I always use ArgoCD for installing something in the Kubernetes cluster, so here is a manifest: apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
  name: vector
  namespace: argocd
spec:
  project: default
  syncPolicy:
    automated:
      prune: true
      selfHeal: true
    syncOptions:
      - CreateNamespace=true
    retry:
      limit: 2
      backoff:
        duration: 2s
        factor: 2
        maxDuration: 1m
  destination:
    namespace: logging
    server: 'https://kubernetes.default.svc'
  source:
    repoURL: https://helm.vector.dev
    chart: vector
    targetRevision: 0.25.0
    helm:
      values: |
        service:
          enabled: false
        serviceAccount:
          annotations:
            eks.amazonaws.com/role-arn: arn:aws:iam::YOUR_ID:role/eks-alb-ingress-controller
        customConfig:
          transforms:
            alb:
              type: remap
              inputs:
                - s3
              source: >-
                structured =
                  parse_regex!(.message, r'^(?P<Type>[^ ]*) (?P<Time>[^ ]*) (?P<Alb>[^ ]*) (?P<ClientIP>[^ ]*):(?P<ClientPort>[0-9]*) (?P<TargetIP>[^ ]*)[:-](?P<TargetPort>[0-9]*) (?P<RequestProcessingTime>[-.0-9]*) (?P<TargetProcessingTime>[-.0-9]*) (?P<ResponseProcessingTime>[-.0-9]*) (?P<StatusCode>|[-0-9]*) (?P<TargetStatusCode>-|[-0-9]*) (?P<ReceivedBytes>[-0-9]*) (?P<SentBytes>[-0-9]*) \"(?P<RequestVerb>[^ ]*) (?P<RequestUrl>.*) (?P<RequestProto>- |[^ ]*)\" \"(?P<UserAgent>[^\"]*)\" (?P<SslCipher>[A-Z0-9-_]+) (?P<SslProtocol>[A-Za-z0-9.-]*) (?P<TargetGroupArn>[^ ]*) \"(?P<TraceId>[^\"]*)\" \"(?P<DomainName>[^\"]*)\" \"(?P<CertArn>[^\"]*)\" (?P<MatchedRulePriority>[-.0-9]*) (?P<RequestCreationTime>[^ ]*) \"(?P<ActionExecuted>[^\"]*)\" \"(?P<RedirectUrl>[^\"]*)\" \"(?P<LambdaErrorReason>[^ ]*)\" \"(?P<TargetPortList>[^\s]+?)\" \"(?P<TargetStatusCodeList>[^\s]+)\" \"(?P<Classification>[^ ]*)\" \"(?P<Classificationreason>[^ ]*)\"')
                . = merge(., structured)

                .ReceivedBytes = to_int!(.ReceivedBytes)
                .RequestProcessingTime = to_float!(.RequestProcessingTime)
                .ResponseProcessingTime = to_float!(.ResponseProcessingTime)
                .StatusCode = to_int!(.StatusCode)
                .SentBytes = to_int!(.SentBytes)
                .TargetProcessingTime = to_float!(.TargetProcessingTime)

                parsed_url, err = parse_url(.RequestUrl)
                if err == null {
                  .Path = parsed_url.path
                  .RequestDomainName = parsed_url.host
                }
          sources:
            s3:
              type: aws_s3
              compression: auto
              strategy: sqs
              region: "us-east-1"
              sqs:
                delete_message: true
                poll_secs: 5
                visibility_timeout_secs: 300
                queue_url: "https://sqs.us-east-1.amazonaws.com/YOUR_ID/alb-logs"
          sinks:
            opensearch:
              type: elasticsearch
              endpoints:
                - "https://YOUR_OPENSEARCH_URL.us-east-1.es.amazonaws.com"
              inputs:
                - alb 4. Enabling Our Logs There are three ways you can enable logging: Old-fashioned documentation from AWS - link With Terraform aws_lb resource - link And the easiest way is - Kubernetes Ingress annotation (our way): alb.ingress.kubernetes.io/load-balancer-attributes: access_logs.s3.enabled=true,access_logs.s3.bucket=alb-logs Now, you should be able to see logs in your OpenSearch console! That`s all! Greetings Comrades! One of the strangest logging setups I ever had - AWS ALB controller logs. Really, look at the scheme: 1. S3 Bucket for ALB Logs I assume that you already have an ALB Controller in your EKS Cluster. So, we should create an S3 bucket and enable the SQS trigger with Terraform: ###
# ALB Controller Logs S3 Bucket
###

resource "aws_s3_bucket" "alb_logs" {
  bucket = "alb-logs"
}

resource "aws_s3_bucket_lifecycle_configuration" "alb_logs" {
  bucket = aws_s3_bucket.alb_logs.id

  rule {
    id = "log"

    expiration {
      days = 3
    }

    status = "Enabled"
  }
}

resource "aws_s3_bucket_policy" "alb_logs" {
  bucket = aws_s3_bucket.alb_logs.id
  policy = data.aws_iam_policy_document.alb_logs_bucket_policy.json
}

data "aws_iam_policy_document" "alb_logs_bucket_policy" {
  statement {
    principals {
      type        = "AWS"
      identifiers = ["arn:aws:iam::127311923021:root"] <--- it should be like this!!!
    }
    actions   = ["s3:*"]   <--- I`m so lazy
    resources = ["${aws_s3_bucket.alb_logs.arn}/*", ]
  }
} ###
# ALB Controller Logs S3 Bucket
###

resource "aws_s3_bucket" "alb_logs" {
  bucket = "alb-logs"
}

resource "aws_s3_bucket_lifecycle_configuration" "alb_logs" {
  bucket = aws_s3_bucket.alb_logs.id

  rule {
    id = "log"

    expiration {
      days = 3
    }

    status = "Enabled"
  }
}

resource "aws_s3_bucket_policy" "alb_logs" {
  bucket = aws_s3_bucket.alb_logs.id
  policy = data.aws_iam_policy_document.alb_logs_bucket_policy.json
}

data "aws_iam_policy_document" "alb_logs_bucket_policy" {
  statement {
    principals {
      type        = "AWS"
      identifiers = ["arn:aws:iam::127311923021:root"] <--- it should be like this!!!
    }
    actions   = ["s3:*"]   <--- I`m so lazy
    resources = ["${aws_s3_bucket.alb_logs.arn}/*", ]
  }
} 2. S3 Trigger to SQS Queue ###
# ALB Logs SQS Queue
###

resource "aws_sqs_queue" "alb_logs" {
  name                    = "alb-logs"
  sqs_managed_sse_enabled = false
}

data "aws_iam_policy_document" "alb_logs_policy" {
  statement {
    effect = "Allow"

    principals {
      type        = "*"   <--- Wow again!!!
      identifiers = ["*"]   <--- And again!!!
    }

    actions   = ["sqs:SendMessage"]
    resources = [aws_sqs_queue.alb_logs.arn]

    condition {
      test     = "ArnEquals"
      variable = "aws:SourceArn"
      values   = [aws_s3_bucket.alb_logs.arn]
    }
  }
}

resource "aws_sqs_queue_policy" "alb_logs" {
  queue_url = aws_sqs_queue.alb_logs.id
  policy    = data.aws_iam_policy_document.alb_logs_policy.json
}

resource "aws_s3_bucket_notification" "alb_logs" {
  bucket = aws_s3_bucket.alb_logs.id

  queue {
    id        = "alb-logs"
    queue_arn = aws_sqs_queue.alb_logs.arn
    events    = ["s3:ObjectCreated:*"]
  }
} ###
# ALB Logs SQS Queue
###

resource "aws_sqs_queue" "alb_logs" {
  name                    = "alb-logs"
  sqs_managed_sse_enabled = false
}

data "aws_iam_policy_document" "alb_logs_policy" {
  statement {
    effect = "Allow"

    principals {
      type        = "*"   <--- Wow again!!!
      identifiers = ["*"]   <--- And again!!!
    }

    actions   = ["sqs:SendMessage"]
    resources = [aws_sqs_queue.alb_logs.arn]

    condition {
      test     = "ArnEquals"
      variable = "aws:SourceArn"
      values   = [aws_s3_bucket.alb_logs.arn]
    }
  }
}

resource "aws_sqs_queue_policy" "alb_logs" {
  queue_url = aws_sqs_queue.alb_logs.id
  policy    = data.aws_iam_policy_document.alb_logs_policy.json
}

resource "aws_s3_bucket_notification" "alb_logs" {
  bucket = aws_s3_bucket.alb_logs.id

  queue {
    id        = "alb-logs"
    queue_arn = aws_sqs_queue.alb_logs.arn
    events    = ["s3:ObjectCreated:*"]
  }
} 3.  Installing and Configuring Vector I always use ArgoCD for installing something in the Kubernetes cluster, so here is a manifest: apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
  name: vector
  namespace: argocd
spec:
  project: default
  syncPolicy:
    automated:
      prune: true
      selfHeal: true
    syncOptions:
      - CreateNamespace=true
    retry:
      limit: 2
      backoff:
        duration: 2s
        factor: 2
        maxDuration: 1m
  destination:
    namespace: logging
    server: 'https://kubernetes.default.svc'
  source:
    repoURL: https://helm.vector.dev
    chart: vector
    targetRevision: 0.25.0
    helm:
      values: |
        service:
          enabled: false
        serviceAccount:
          annotations:
            eks.amazonaws.com/role-arn: arn:aws:iam::YOUR_ID:role/eks-alb-ingress-controller
        customConfig:
          transforms:
            alb:
              type: remap
              inputs:
                - s3
              source: >-
                structured =
                  parse_regex!(.message, r'^(?P<Type>[^ ]*) (?P<Time>[^ ]*) (?P<Alb>[^ ]*) (?P<ClientIP>[^ ]*):(?P<ClientPort>[0-9]*) (?P<TargetIP>[^ ]*)[:-](?P<TargetPort>[0-9]*) (?P<RequestProcessingTime>[-.0-9]*) (?P<TargetProcessingTime>[-.0-9]*) (?P<ResponseProcessingTime>[-.0-9]*) (?P<StatusCode>|[-0-9]*) (?P<TargetStatusCode>-|[-0-9]*) (?P<ReceivedBytes>[-0-9]*) (?P<SentBytes>[-0-9]*) \"(?P<RequestVerb>[^ ]*) (?P<RequestUrl>.*) (?P<RequestProto>- |[^ ]*)\" \"(?P<UserAgent>[^\"]*)\" (?P<SslCipher>[A-Z0-9-_]+) (?P<SslProtocol>[A-Za-z0-9.-]*) (?P<TargetGroupArn>[^ ]*) \"(?P<TraceId>[^\"]*)\" \"(?P<DomainName>[^\"]*)\" \"(?P<CertArn>[^\"]*)\" (?P<MatchedRulePriority>[-.0-9]*) (?P<RequestCreationTime>[^ ]*) \"(?P<ActionExecuted>[^\"]*)\" \"(?P<RedirectUrl>[^\"]*)\" \"(?P<LambdaErrorReason>[^ ]*)\" \"(?P<TargetPortList>[^\s]+?)\" \"(?P<TargetStatusCodeList>[^\s]+)\" \"(?P<Classification>[^ ]*)\" \"(?P<Classificationreason>[^ ]*)\"')
                . = merge(., structured)

                .ReceivedBytes = to_int!(.ReceivedBytes)
                .RequestProcessingTime = to_float!(.RequestProcessingTime)
                .ResponseProcessingTime = to_float!(.ResponseProcessingTime)
                .StatusCode = to_int!(.StatusCode)
                .SentBytes = to_int!(.SentBytes)
                .TargetProcessingTime = to_float!(.TargetProcessingTime)

                parsed_url, err = parse_url(.RequestUrl)
                if err == null {
                  .Path = parsed_url.path
                  .RequestDomainName = parsed_url.host
                }
          sources:
            s3:
              type: aws_s3
              compression: auto
              strategy: sqs
              region: "us-east-1"
              sqs:
                delete_message: true
                poll_secs: 5
                visibility_timeout_secs: 300
                queue_url: "https://sqs.us-east-1.amazonaws.com/YOUR_ID/alb-logs"
          sinks:
            opensearch:
              type: elasticsearch
              endpoints:
                - "https://YOUR_OPENSEARCH_URL.us-east-1.es.amazonaws.com"
              inputs:
                - alb apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
  name: vector
  namespace: argocd
spec:
  project: default
  syncPolicy:
    automated:
      prune: true
      selfHeal: true
    syncOptions:
      - CreateNamespace=true
    retry:
      limit: 2
      backoff:
        duration: 2s
        factor: 2
        maxDuration: 1m
  destination:
    namespace: logging
    server: 'https://kubernetes.default.svc'
  source:
    repoURL: https://helm.vector.dev
    chart: vector
    targetRevision: 0.25.0
    helm:
      values: |
        service:
          enabled: false
        serviceAccount:
          annotations:
            eks.amazonaws.com/role-arn: arn:aws:iam::YOUR_ID:role/eks-alb-ingress-controller
        customConfig:
          transforms:
            alb:
              type: remap
              inputs:
                - s3
              source: >-
                structured =
                  parse_regex!(.message, r'^(?P<Type>[^ ]*) (?P<Time>[^ ]*) (?P<Alb>[^ ]*) (?P<ClientIP>[^ ]*):(?P<ClientPort>[0-9]*) (?P<TargetIP>[^ ]*)[:-](?P<TargetPort>[0-9]*) (?P<RequestProcessingTime>[-.0-9]*) (?P<TargetProcessingTime>[-.0-9]*) (?P<ResponseProcessingTime>[-.0-9]*) (?P<StatusCode>|[-0-9]*) (?P<TargetStatusCode>-|[-0-9]*) (?P<ReceivedBytes>[-0-9]*) (?P<SentBytes>[-0-9]*) \"(?P<RequestVerb>[^ ]*) (?P<RequestUrl>.*) (?P<RequestProto>- |[^ ]*)\" \"(?P<UserAgent>[^\"]*)\" (?P<SslCipher>[A-Z0-9-_]+) (?P<SslProtocol>[A-Za-z0-9.-]*) (?P<TargetGroupArn>[^ ]*) \"(?P<TraceId>[^\"]*)\" \"(?P<DomainName>[^\"]*)\" \"(?P<CertArn>[^\"]*)\" (?P<MatchedRulePriority>[-.0-9]*) (?P<RequestCreationTime>[^ ]*) \"(?P<ActionExecuted>[^\"]*)\" \"(?P<RedirectUrl>[^\"]*)\" \"(?P<LambdaErrorReason>[^ ]*)\" \"(?P<TargetPortList>[^\s]+?)\" \"(?P<TargetStatusCodeList>[^\s]+)\" \"(?P<Classification>[^ ]*)\" \"(?P<Classificationreason>[^ ]*)\"')
                . = merge(., structured)

                .ReceivedBytes = to_int!(.ReceivedBytes)
                .RequestProcessingTime = to_float!(.RequestProcessingTime)
                .ResponseProcessingTime = to_float!(.ResponseProcessingTime)
                .StatusCode = to_int!(.StatusCode)
                .SentBytes = to_int!(.SentBytes)
                .TargetProcessingTime = to_float!(.TargetProcessingTime)

                parsed_url, err = parse_url(.RequestUrl)
                if err == null {
                  .Path = parsed_url.path
                  .RequestDomainName = parsed_url.host
                }
          sources:
            s3:
              type: aws_s3
              compression: auto
              strategy: sqs
              region: "us-east-1"
              sqs:
                delete_message: true
                poll_secs: 5
                visibility_timeout_secs: 300
                queue_url: "https://sqs.us-east-1.amazonaws.com/YOUR_ID/alb-logs"
          sinks:
            opensearch:
              type: elasticsearch
              endpoints:
                - "https://YOUR_OPENSEARCH_URL.us-east-1.es.amazonaws.com"
              inputs:
                - alb 4. Enabling Our Logs There are three ways you can enable logging: Old-fashioned documentation from AWS - link Old-fashioned documentation from AWS - link link With Terraform aws_lb resource - link With Terraform aws_lb resource - link link And the easiest way is - Kubernetes Ingress annotation (our way): And the easiest way is - Kubernetes Ingress annotation (our way): alb.ingress.kubernetes.io/load-balancer-attributes: access_logs.s3.enabled=true,access_logs.s3.bucket=alb-logs alb.ingress.kubernetes.io/load-balancer-attributes: access_logs.s3.enabled=true,access_logs.s3.bucket=alb-logs Now, you should be able to see logs in your OpenSearch console! That`s all!

ALB Controller Logs With Vector and OpenSearch: A Guide

100x Simpler -  The Ultimate Open-Source Guide

Get Rich Building Verticalized AI Wrappers (Even If You Don’t Code)

রিচ বিল্ডিং ভার্টিক্যালাইজড এআই র‍্যাপার পান (এমনকি যদি আপনি কোড না করেন)

Werden Sie reich durch die Entwicklung vertikaler KI-Wrapper (auch wenn Sie nicht programmieren können)

Hazte rico creando contenedores de IA verticalizados (aunque no sepas programar)

Devenez riche en créant des wrappers d’IA verticalisés (même si vous ne codez pas)

वर्टिकलाइज़्ड AI रैपर बनाकर अमीर बनें (भले ही आप कोड न जानते हों)

Menjadi Kaya dengan Membangun Pembungkus AI Vertikal (Bahkan Jika Anda Tidak Membuat Kode)

垂直統合型 AI ラッパーを構築して金持ちになる (コードを書かなくても)

Rich Building вертикалдандырылған AI орауыштарын алыңыз (тіпті кодтамасаңыз да)

수직화된 AI 래퍼를 구축하여 부자가 되세요(코딩하지 않아도)

Баян барилгын босоо AI боодолтой бол (та код бичээгүй байсан ч)

Fique rico construindo wrappers de IA verticalizados (mesmo que você não codifique)

Разбогатейте, создавая вертикальные оболочки ИИ (даже если вы не пишете код)

Hel dhismo qani ah oo toosan AI ku duub (Xitaa Haddi aadan Codayn)

Get Rich Building Verticalized AI Wrappers (Kahit Hindi Ka Mag-code)

Dikey AI Sarmalayıcıları Oluşturarak Zengin Olun (Kodlamasanız Bile)

رچ بلڈنگ ورٹیکلائزڈ AI ریپر حاصل کریں (چاہے آپ کوڈ نہ بھی کریں)

Làm giàu bằng cách xây dựng các trình bao bọc AI theo chiều dọc (ngay cả khi bạn không viết mã)

通过构建垂直化 AI 包装器致富（即使你不会编码）

Hey Hackers, Sprinto has been nominated for HackerNoon's Startup of the Year 2024 awards in San Francisco, under the Data Privacy And Compliance category. Please vote for us here: https://hackernoon.com/startups/industry/data-privacy-and-compliance?stup=66b3ed0434a7dea7f8f8389e&embedable=true Meet Sprinto Sprinto is in the business of security compliance for fast-growing companies. Thousands of ambitious businesses rely on Sprinto to automate and streamline risk and compliance management. Sprinto supports major security frameworks like SOC 2, ISO 27001, GDPR, HIPAA, and PCI-DSS, as well as custom, industry-specific standards. With ready-to-use tools and templates, plus intelligent features such as smart workflows, adaptive automation, and AI, Sprinto provides a complete toolkit for navigating infosec risk and regulatory requirements— ensuring compliance and audits never hinder growth. We are on a mission to help businesses with continuous compliance, healthy operational practices, and the ability to grow and scale with unwavering confidence. How Sprinto achieved product-market fit Sprinto was born from a problem we experienced firsthand. Back when we were running Recruiterbox, compliance was a constant, nagging challenge that seemed to pull us away from what mattered most. We spent countless hours manually managing requirements, feeling how it drained our team’s energy and slowed down our growth. It became clear that we weren’t the only ones struggling—compliance was holding so many companies back. Determined to make a difference, we set out to build Sprinto, but we knew we couldn’t do it alone. From the start, we partnered closely with a small group of beta customers who became our co-creators in the process. They shared their frustrations and guided us to understand their biggest pain points. Their feedback was raw and direct, pushing us to get it right. Together with our early customers, we shaped Sprinto into a tool that didn’t just meet the requirements—it made compliance feel manageable, intuitive, and even empowering. Sprinto’s journey to product-market fit was deeply personal and powered by real-world insights. We’re proud that it’s a platform built out of experience, forged in partnership, and dedicated to making compliance simple and effective. It’s more than a product; it’s a solution we wished we’d had all along. The Evolution of Sprinto Sprinto’s journey began with our Co-founders, Girish Redekar and Raghuveer Kancherla, drawing from their experience at Recruiterbox. They had firsthand knowledge of how daunting and tedious compliance could be, and they set out to change that with Sprinto. As Girish puts it, “The very first wall I hit was deciphering security questionnaires for enterprise deals. We were doing great, signing new clients, and then—bam!—we got hit with these detailed security reviews. Sure, we had solid security in place, but explaining it clearly to enterprise clients? That was a whole different story.” Girish recalls sitting through calls, confidently answering questions about their security practices, only to be thrown off by sophisticated jargon that left them scrambling. It wasn’t until he reached out to fellow founders for guidance that things started to click. This experience opened their eyes to a huge gap in the market—companies of all sizes were struggling with compliance, and they needed someone who could help them navigate the complex process without the steep learning curve. That realization is what led to the creation of Sprinto, a solution built to guide businesses through the intricate maze of compliance with ease and confidence. Milestones and achievements Lessons learned From day one, we knew Sprinto’s success depended on more than just hiring the right people—it was about building a team grounded in shared values and commitment to our mission, which is also why you’ll see our hiring process is unlike any other you’ve seen. We invested time and resources to find individuals whose skills and personalities aligned with our vision, creating a team that’s as resilient as it is innovative. Their adaptability has been the driving force behind Sprinto’s growth. We also discovered early that customer delight wasn’t just a checkbox; it had to be our guiding star. Every update, every feature, every tweak was designed with one goal in mind: to exceed expectations. Listening, iterating, and prioritizing customer experience turned Sprinto into a platform that feels tailor-made for its users, not just functional but something that helps scale our customers’ businesses. Of course, we faced significant challenges along the way. Rapid scaling brought growing pains, teaching us that sustainable growth requires robust processes and a grounded team culture. Building trust in a security-driven industry was another hurdle, but transparency became our most valuable asset. By delivering tangible value, we converted doubt into confidence and learned the power of authenticity. Each lesson, challenge, and success has shaped Sprinto into what it is today—a platform built not just for today’s needs but tomorrow’s, too. We move forward with a commitment to evolving alongside our customers, continually redefining what’s possible in this space. What Startups of The Year means to us At Sprinto, this nomination feels like a big milestone in our journey. It’s a chance for us to share what we've built, learn from fellow innovators, and connect with partners who can truly benefit from what we do. But more than anything, it’s a moment to recognize our incredible team—the people who show up every day, staying focused and delivering, no matter what. As we grow, it only gets harder to keep the same energy, values, and momentum that started it all. But this recognition, alongside everything we’ve achieved so far, reminds us why we’re here: to revolutionize the GRC space. And we’re not slowing down anytime soon. We are extremely humbled and immensely proud to support thousands of businesses—from young, enterprising startups to established enterprises—in seeding, streamlining, and scaling one of the most complex yet critical aspects of any successful business: trust. We invite you to support our vision by voting for Sprinto and joining us in shaping the future of compliance. Vote for us today! Hey Hackers, Sprinto has been nominated for HackerNoon's Startup of the Year 2024 awards in San Francisco, under the Data Privacy And Compliance category. HackerNoon's Startup of the Year 2024 HackerNoon's Startup of the Year 2024 Please vote for us here: https://hackernoon.com/startups/industry/data-privacy-and-compliance?stup=66b3ed0434a7dea7f8f8389e&embedable=true https://hackernoon.com/startups/industry/data-privacy-and-compliance?stup=66b3ed0434a7dea7f8f8389e&embedable=true Meet Sprinto Sprinto is in the business of security compliance for fast-growing companies. Thousands of ambitious businesses rely on Sprinto to automate and streamline risk and compliance management. Sprinto supports major security frameworks like SOC 2, ISO 27001, GDPR, HIPAA, and PCI-DSS, as well as custom, industry-specific standards. With ready-to-use tools and templates, plus intelligent features such as smart workflows, adaptive automation, and AI, Sprinto provides a complete toolkit for navigating infosec risk and regulatory requirements— ensuring compliance and audits never hinder growth. We are on a mission to help businesses with continuous compliance, healthy operational practices, and the ability to grow and scale with unwavering confidence. How Sprinto achieved product-market fit How Sprinto achieved product-market fit Sprinto was born from a problem we experienced firsthand. Back when we were running Recruiterbox, compliance was a constant, nagging challenge that seemed to pull us away from what mattered most. We spent countless hours manually managing requirements, feeling how it drained our team’s energy and slowed down our growth. It became clear that we weren’t the only ones struggling—compliance was holding so many companies back. Determined to make a difference, we set out to build Sprinto, but we knew we couldn’t do it alone. From the start, we partnered closely with a small group of beta customers who became our co-creators in the process. They shared their frustrations and guided us to understand their biggest pain points. Their feedback was raw and direct, pushing us to get it right. Together with our early customers, we shaped Sprinto into a tool that didn’t just meet the requirements—it made compliance feel manageable, intuitive, and even empowering. Sprinto’s journey to product-market fit was deeply personal and powered by real-world insights. We’re proud that it’s a platform built out of experience, forged in partnership, and dedicated to making compliance simple and effective. It’s more than a product; it’s a solution we wished we’d had all along. The Evolution of Sprinto The Evolution of Sprinto Sprinto’s journey began with our Co-founders, Girish Redekar and Raghuveer Kancherla, drawing from their experience at Recruiterbox. They had firsthand knowledge of how daunting and tedious compliance could be, and they set out to change that with Sprinto. As Girish puts it, “The very first wall I hit was deciphering security questionnaires for enterprise deals. We were doing great, signing new clients, and then—bam!—we got hit with these detailed security reviews. Sure, we had solid security in place, but explaining it clearly to enterprise clients? That was a whole different story.” “The very first wall I hit was deciphering security questionnaires for enterprise deals. We were doing great, signing new clients, and then—bam!—we got hit with these detailed security reviews. Sure, we had solid security in place, but explaining it clearly to enterprise clients? That was a whole different story.” Girish recalls sitting through calls, confidently answering questions about their security practices, only to be thrown off by sophisticated jargon that left them scrambling. It wasn’t until he reached out to fellow founders for guidance that things started to click. This experience opened their eyes to a huge gap in the market—companies of all sizes were struggling with compliance, and they needed someone who could help them navigate the complex process without the steep learning curve. That realization is what led to the creation of Sprinto, a solution built to guide businesses through the intricate maze of compliance with ease and confidence. Milestones and achievements Milestones and achievements Lessons learned Lessons learned From day one, we knew Sprinto’s success depended on more than just hiring the right people—it was about building a team grounded in shared values and commitment to our mission, which is also why you’ll see our hiring process is unlike any other you’ve seen. We invested time and resources to find individuals whose skills and personalities aligned with our vision, creating a team that’s as resilient as it is innovative. Their adaptability has been the driving force behind Sprinto’s growth. We also discovered early that customer delight wasn’t just a checkbox; it had to be our guiding star. Every update, every feature, every tweak was designed with one goal in mind: to exceed expectations. Listening, iterating, and prioritizing customer experience turned Sprinto into a platform that feels tailor-made for its users, not just functional but something that helps scale our customers’ businesses. Of course, we faced significant challenges along the way. Rapid scaling brought growing pains, teaching us that sustainable growth requires robust processes and a grounded team culture. Building trust in a security-driven industry was another hurdle, but transparency became our most valuable asset. By delivering tangible value, we converted doubt into confidence and learned the power of authenticity. Each lesson, challenge, and success has shaped Sprinto into what it is today—a platform built not just for today’s needs but tomorrow’s, too. We move forward with a commitment to evolving alongside our customers, continually redefining what’s possible in this space. What Startups of The Year means to us What Startups of The Year means to us At Sprinto, this nomination feels like a big milestone in our journey. It’s a chance for us to share what we've built, learn from fellow innovators, and connect with partners who can truly benefit from what we do. But more than anything, it’s a moment to recognize our incredible team—the people who show up every day, staying focused and delivering, no matter what. As we grow, it only gets harder to keep the same energy, values, and momentum that started it all. But this recognition, alongside everything we’ve achieved so far, reminds us why we’re here: to revolutionize the GRC space. And we’re not slowing down anytime soon. We are extremely humbled and immensely proud to support thousands of businesses—from young, enterprising startups to established enterprises—in seeding, streamlining, and scaling one of the most complex yet critical aspects of any successful business: trust. We invite you to support our vision by voting for Sprinto and joining us in shaping the future of compliance. Vote for us today! Vote for us today ! Vote for us today

Meet Sprinto, Startups of the Year 2024 Nominee

What happens when users get distracted by everything but an app? Why should anyone care about a product when there’s no reason to? These are the questions I often ask myself as I work with different brands. It’s even tougher in the summer. The sun’s out, people are on vacation, and your app is the last thing on their minds. We saw this firsthand with a well-known pizza delivery service — their customers weren’t exactly dreaming of pepperoni between beach trips. So, how do you keep people interested when pizza isn't their priority? You get creative. And by creative, I’m talking about transforming the way people interact with your brand, giving them a reason to check in just for fun. We wanted people to stay engaged and loyal, while also driving more pizza orders. To make that happen, we needed something fresh to keep them coming back. Turning Summer into a Game So, picture this: it’s mid-June, and you’re a pizza company. Sales are down because people are on holiday mode. What do you do? Cut prices? Send out boring email promos? Nah. Instead, they flipped the concept of the holiday advent calendar — a tradition people associate with Christmas — and dropped it into the middle of summer. I know, it sounds a little wild. But that’s the point. They turned each day into a mini game. Customers would open the pizza app daily, like a digital advent calendar, and uncover two key elements behind each "door." Game Mechanics in Action First, a new postcard: each day featured a unique postcard, which users could collect, customize, or share with friends. These weren’t just generic images — there were three types of postcards to keep things fresh: illustrative postcards with custom designs, city-specific postcards featuring local landmarks depending on the user’s location, and customizable postcards, where users could upload their own photos, adding a personal touch. Along with the postcard, users would receive a daily promotion, like a reduced price on a specific product. This wasn’t just about discounts, though. It was about adding a tangible reward to the game, encouraging users to open the app every day and take advantage of the deals while enjoying the fun, personalized content. This mechanic plays directly into a behavioral principle called the variable reward system. When you scroll through your news feed, you don’t know what new story or post you’ll see next. This unpredictability is addictive. So, our pizza delivery service made it fun to keep checking in, day after day. The idea wasn’t new, but it was placed in a fresh, unexpected context. And it worked. Over half of the pizza app users joined in, with participation peaking around lunch and after work. Users created and shared more than 1 million postcards, adding a social twist. In total, the campaign drew 880,000 participants across Europe and Asia. Why It Worked: The Power of Dopamine Let’s get real. People are wired for rewards, especially when they don’t know exactly what they’re getting. When users opened that app and saw a fresh offer, it wasn’t just about the discount — it was about the dopamine hit that comes with curiosity. That’s something brands like Spotify and TikTok have nailed with their recommendation algorithms. It’s not the certainty of what’s next, but the excitement of discovering it. The advent mechanic we created together tapped into that same feeling. And the best part? The offers felt more like little gifts, not desperate promos. This shifted the perception of value for customers. It wasn’t "buy now," but "here’s something special just for today”. Building Engagement Isn’t Just for Pizza Now, I’ve worked with in-app engagement for a long time, and I can tell you this: the mechanic isn’t limited to pizzas or food delivery. Any brand with an app can implement it. For example, I’ve seen fitness apps that give users daily challenges to unlock personalized workouts or nutrition tips. And it works. Why? Because it makes people want to come back, even if they weren’t originally planning to. I once joked with the team that we could put a picture of a puppy behind one of the digital calendar doors, and the next day our daily active users would triple. Who can resist puppies? I never tested it, but if you try, let me know how it goes. Whether you’re running an eCommerce app, a B2B SaaS platform, or even a content-driven site, you can use these tactics. Here’s how: Make it fun: Your engagement tactics don’t need to feel like work. Offer users something they don’t expect.
Add surprise: Use the variable reward principle. People love surprises. If they don’t know what they’re getting, they’re more likely to come back.
Keep it light: No one wants to feel spammed or manipulated. Make your gamification subtle and rewarding, not sales-y.
Build habits: Think fitness apps or loyalty programs. It’s not just about engagement today. It’s about getting your users to come back tomorrow and the day after. What did I learn from this experience? People crave excitement and engagement — not just products. As a marketer, it’s not your job to just “sell” something; it’s about creating an experience that people actually enjoy. The pizza delivery service’s digital advent calendar was a hit because it took something simple and transformed it into a daily delight. And it’s something any company can do. What We Learned: How to Keep Users Engaged So, what can you do to make your users look forward to engaging with your brand, even when they don’t need to? You don’t have to reinvent the wheel. Just take something familiar, make it fun, and watch as your users turn into daily fans: Don’t be afraid to experiment Sometimes the boldest ideas, like launching a summer advent calendar, are the ones that pay off. Try unconventional tactics Go beyond the usual promos. Interactive tools like skill wheels or daily challenges can keep things fresh. Make it a habit Use gamification to build routines. Daily rewards give people a reason to keep coming back. Surprise your users Everyone loves surprises. Small, unexpected rewards keep users engaged and curious. Personal touches matter Personalization, like custom postcards, adds a unique connection that keeps users interested. And hey, if all else fails, try the puppies. What happens when users get distracted by everything but an app? Why should anyone care about a product when there’s no reason to? These are the questions I often ask myself as I work with different brands. What happens when users get distracted by everything but an app? Why should anyone care about a product when there’s no reason to? These are the questions I often ask myself as I work with different brands. It’s even tougher in the summer. The sun’s out, people are on vacation, and your app is the last thing on their minds. We saw this firsthand with a well-known pizza delivery service — their customers weren’t exactly dreaming of pepperoni between beach trips. So, how do you keep people interested when pizza isn't their priority? You get creative. And by creative, I’m talking about transforming the way people interact with your brand, giving them a reason to check in just for fun. We wanted people to stay engaged and loyal, while also driving more pizza orders. To make that happen, we needed something fresh to keep them coming back. Turning Summer into a Game Turning Summer into a Game So, picture this: it’s mid-June, and you’re a pizza company. Sales are down because people are on holiday mode. What do you do? Cut prices? Send out boring email promos? Nah. Instead, they flipped the concept of the holiday advent calendar — a tradition people associate with Christmas — and dropped it into the middle of summer. I know, it sounds a little wild. But that’s the point. They turned each day into a mini game. Customers would open the pizza app daily, like a digital advent calendar, and uncover two key elements behind each "door." Game Mechanics in Action Game Mechanics in Action First, a new postcard: each day featured a unique postcard, which users could collect, customize, or share with friends. These weren’t just generic images — there were three types of postcards to keep things fresh: illustrative postcards with custom designs, city-specific postcards featuring local landmarks depending on the user’s location, and customizable postcards, where users could upload their own photos, adding a personal touch. Along with the postcard, users would receive a daily promotion, like a reduced price on a specific product. This wasn’t just about discounts, though. It was about adding a tangible reward to the game, encouraging users to open the app every day and take advantage of the deals while enjoying the fun, personalized content . personalized content This mechanic plays directly into a behavioral principle called the variable reward system. When you scroll through your news feed, you don’t know what new story or post you’ll see next. This unpredictability is addictive. So, our pizza delivery service made it fun to keep checking in, day after day. The idea wasn’t new, but it was placed in a fresh, unexpected context. And it worked. Over half of the pizza app users joined in, with participation peaking around lunch and after work. Users created and shared more than 1 million postcards, adding a social twist. In total, the campaign drew 880,000 participants across Europe and Asia. Why It Worked: The Power of Dopamine Let’s get real. People are wired for rewards, especially when they don’t know exactly what they’re getting. When users opened that app and saw a fresh offer, it wasn’t just about the discount — it was about the dopamine hit that comes with curiosity. That’s something brands like Spotify and TikTok have nailed with their recommendation algorithms . It’s not the certainty of what’s next, but the excitement of discovering it. The advent mechanic we created together tapped into that same feeling. TikTok have nailed with their recommendation algorithms TikTok have nailed with their recommendation algorithms And the best part? The offers felt more like little gifts, not desperate promos. This shifted the perception of value for customers. It wasn’t "buy now," but "here’s something special just for today”. Building Engagement Isn’t Just for Pizza Now, I’ve worked with in-app engagement for a long time, and I can tell you this: the mechanic isn’t limited to pizzas or food delivery. Any brand with an app can implement it. For example, I’ve seen fitness apps that give users daily challenges to unlock personalized workouts or nutrition tips. And it works. Why? Because it makes people want to come back, even if they weren’t originally planning to. I once joked with the team that we could put a picture of a puppy behind one of the digital calendar doors, and the next day our daily active users would triple. Who can resist puppies? I never tested it, but if you try, let me know how it goes. Whether you’re running an eCommerce app, a B2B SaaS platform, or even a content-driven site, you can use these tactics. Here’s how: Make it fun: Your engagement tactics don’t need to feel like work. Offer users something they don’t expect. Add surprise: Use the variable reward principle. People love surprises. If they don’t know what they’re getting, they’re more likely to come back. Keep it light: No one wants to feel spammed or manipulated. Make your gamification subtle and rewarding, not sales-y. Build habits: Think fitness apps or loyalty programs. It’s not just about engagement today. It’s about getting your users to come back tomorrow and the day after. Make it fun : Your engagement tactics don’t need to feel like work. Offer users something they don’t expect. Make it fun Add surprise : Use the variable reward principle. People love surprises. If they don’t know what they’re getting, they’re more likely to come back. Add surprise Keep it light : No one wants to feel spammed or manipulated. Make your gamification subtle and rewarding, not sales-y. Keep it light Build habits : Think fitness apps or loyalty programs. It’s not just about engagement today. It’s about getting your users to come back tomorrow and the day after. Build habits What did I learn from this experience? People crave excitement and engagement — not just products. As a marketer, it’s not your job to just “sell” something; it’s about creating an experience that people actually enjoy. The pizza delivery service’s digital advent calendar was a hit because it took something simple and transformed it into a daily delight. And it’s something any company can do. What We Learned: How to Keep Users Engaged So, what can you do to make your users look forward to engaging with your brand, even when they don’t need to? You don’t have to reinvent the wheel. Just take something familiar, make it fun, and watch as your users turn into daily fans: Don’t be afraid to experiment Don’t be afraid to experiment Don’t be afraid to experiment Sometimes the boldest ideas, like launching a summer advent calendar, are the ones that pay off. Try unconventional tactics Try unconventional tactics Try unconventional tactics Go beyond the usual promos. Interactive tools like skill wheels or daily challenges can keep things fresh. Make it a habit Make it a habit Make it a habit Use gamification to build routines. Daily rewards give people a reason to keep coming back. Surprise your users Surprise your users Surprise your users Everyone loves surprises. Small, unexpected rewards keep users engaged and curious. Personal touches matter Personal touches matter Personal touches matter Personalization, like custom postcards, adds a unique connection that keeps users interested. And hey, if all else fails, try the puppies.

How Gamification in a Mobile App Boosted Pizza Sales During the Off-Season

In Vietnam, Porn Is Better Served and More Accessible Than Starbucks

For years, Vim was my go-to code editor. I discovered it from a friend when I first started to write code during my second year in College and at first, it felt impossible to use. I struggled with even simple things, like figuring out how to quit! But over time, I got used to the commands. Eventually, it became my favorite tool. With Vim, everything is fast and efficient. It is not just an editor, it feels like an extension of my hands. But recently, things changed. As my projects became larger and more complicated, I noticed that Vim wasn’t as smooth to use. I needed new features like autocomplete and better ways to jump between files, but setting those up meant adding plugin after plugin. Every time I made a small change, I risked breaking my setup. I realized I was spending too much time fixing my editor instead of coding. That’s when a friend suggested I try Zed. At first, I didn’t take it seriously, after all, I’d been using Vim for years. But I decided to give it a shot one day, just out of curiosity. The first thing I noticed was how fast and smooth Zed felt. It opened instantly, and navigating through my projects was quick and easy. The interface was simple, with no clutter, and no distractions. I loved how everything felt focused on the code. The real surprise, though, was that Zed supports Vim commands! All the shortcuts I had memorized, like :wq to save and quit or dd to delete a line, worked exactly the same. My fingers didn’t have to learn anything new, which made the switch feel effortless. It was like moving into a new house but finding all my furniture exactly where I wanted it. Another thing that really stood out was Zed’s collaborative features. I work with other developers remotely, and in Vim, collaboration was always clunky. We’d have to share screens or constantly push code to Git. But in Zed, I could invite my teammates into my editor, and we could work on the same code in real-time. It felt smooth like we were sitting next to each other, even though we were miles apart. After using Zed for a few days, I realized something: it gave me everything I loved about Vim but without the hassle. No more spending hours fixing plugins or wrestling with settings. Zed just worked, right out of the box, and kept things simple. At first, I kept going back to Vim, just to make sure I wasn’t rushing into something new. But each time I did, I found myself missing Zed. It was easier, faster, and better suited for the kind of work I’m doing now. Vim will always have a special place in my heart. It’s where I learned to love coding efficiently. But today, Zed feels like the right tool for me. It keeps the best parts of Vim but adds the modern features I need to grow. For now, Zed is my new home. For years, Vim was my go-to code editor. I discovered it from a friend when I first started to write code during my second year in College and at first, it felt impossible to use. I struggled with even simple things, like figuring out how to quit! But over time, I got used to the commands. Eventually, it became my favorite tool. With Vim, everything is fast and efficient. It is not just an editor, it feels like an extension of my hands. But recently, things changed. As my projects became larger and more complicated, I noticed that Vim wasn’t as smooth to use. I needed new features like autocomplete and better ways to jump between files, but setting those up meant adding plugin after plugin. Every time I made a small change, I risked breaking my setup. I realized I was spending too much time fixing my editor instead of coding. That’s when a friend suggested I try Zed . At first, I didn’t take it seriously, after all, I’d been using Vim for years. But I decided to give it a shot one day, just out of curiosity. Zed The first thing I noticed was how fast and smooth Zed felt. It opened instantly, and navigating through my projects was quick and easy. The interface was simple, with no clutter, and no distractions. I loved how everything felt focused on the code. fast and smooth The real surprise, though, was that Zed supports Vim commands ! All the shortcuts I had memorized, like :wq to save and quit or dd to delete a line, worked exactly the same. My fingers didn’t have to learn anything new, which made the switch feel effortless. It was like moving into a new house but finding all my furniture exactly where I wanted it. Zed supports Vim commands :wq dd Another thing that really stood out was Zed’s collaborative features . I work with other developers remotely, and in Vim, collaboration was always clunky. We’d have to share screens or constantly push code to Git. But in Zed, I could invite my teammates into my editor, and we could work on the same code in real-time. It felt smooth like we were sitting next to each other, even though we were miles apart. collaborative features After using Zed for a few days, I realized something: it gave me everything I loved about Vim but without the hassle. No more spending hours fixing plugins or wrestling with settings. Zed just worked, right out of the box, and kept things simple. At first, I kept going back to Vim, just to make sure I wasn’t rushing into something new. But each time I did, I found myself missing Zed. It was easier, faster, and better suited for the kind of work I’m doing now. Vim will always have a special place in my heart. It’s where I learned to love coding efficiently. But today, Zed feels like the right tool for me . It keeps the best parts of Vim but adds the modern features I need to grow. Zed feels like the right tool for me For now, Zed is my new home.

Why I Switched from Vim to Zed

Stories, News & Mentions about OPENSEED

Openseed’s Stories on HackerNoon

Openseed's News & Mentions